unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bozhidar Batsov <bozhidar@batsov.com>
To: Eric Raymond <esr@thyrsus.com>
Cc: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>,
	"Andreas Schwab" <schwab@linux-m68k.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: ESR's intimidatingly huge task list
Date: Fri, 24 Jan 2014 10:56:22 +0200	[thread overview]
Message-ID: <CAM9Zgm0DM4=u8uG09FA-=K9sO8J8+T7hOzpqa-kKmwxaO6=kOg@mail.gmail.com> (raw)
In-Reply-To: <20140123192242.GA13663@thyrsus.com>

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

On 23 January 2014 21:22, Eric S. Raymond <esr@thyrsus.com> wrote:

> Rüdiger Sonderfeld <ruediger@c-plusplus.de>:
> > > They are not identical, for example leading ./ in bzrignore maps to
> > > leading / in gitignore.
> >
> > Are there any other major differences besides this?
>
> None that are used in the Emacs tree.  I researched this when working
> on reposurgeon's bzr support; the only other problem appears to be bzr
> "RE:" expressions.
>
> > I've replaced the ./ with / in bzrignore and use it with git now.
> > If this looks good I'll commit it to trunk.
>
> It might simplify things on conversion day if you don't.
>
> The goal of the final polished conversion is to make it look as though
> git had been in use all along - that way people won't see distracting
> changes in behavior when they check out old revisions.
>
> This means I'm going to have to write some reposurgeon procedure or
> facility to
> map .bzrignores to .gitignores throughout the history.  Having a .gitignore
> already in the tree at final conversion time might complicate that.
>

We already have some .gitignore files lying around so this ship has sailed.
I think it makes sense to merge the proposed changes and remove the
.gitignore files in the subdirectories.
Even now people are using the bzr repo via git-brz and they'd benefit from
a proper .gitignore file.



> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>

[-- Attachment #2: Type: text/html, Size: 2270 bytes --]

  reply	other threads:[~2014-01-24  8:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 16:56 ESR's intimidatingly huge task list Eric S. Raymond
2014-01-11 17:46 ` Bozhidar Batsov
2014-01-11 18:10   ` Rüdiger Sonderfeld
2014-01-11 18:26     ` Andreas Schwab
2014-01-23 18:47       ` Rüdiger Sonderfeld
2014-01-23 19:22         ` Eric S. Raymond
2014-01-24  8:56           ` Bozhidar Batsov [this message]
2014-01-23 19:25         ` Andreas Schwab
2014-01-11 18:07 ` Rüdiger Sonderfeld
2014-01-11 20:50   ` Eric S. Raymond
2014-01-15 17:31 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM9Zgm0DM4=u8uG09FA-=K9sO8J8+T7hOzpqa-kKmwxaO6=kOg@mail.gmail.com' \
    --to=bozhidar@batsov.com \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=ruediger@c-plusplus.de \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).