all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Should 'old-branches' and 'other-branches' be kept?
Date: Tue, 11 Feb 2014 22:23:44 -0500	[thread overview]
Message-ID: <20140212032344.GA20023@thyrsus.com> (raw)
In-Reply-To: <jwvtxc5umi7.fsf-monnier+emacs@gnu.org>

Stefan Monnier <monnier@iro.umontreal.ca>:
> http://bzr.savannah.gnu.org/r/emacs/README says:
> 
>    [...]
>    `old-branches' Directory of branches that have been merged into trunk already.
>    `other-branches' Directory of various other branches.
>    [...]
> 
> I don't see any point in getting rid of them, tho.

As requested by Andreas Schwab, I'm trying to do lifetime analysis on
the =-prefixed attic files from RCS so they can be renamed and have
correct deletion points.  There are plenty of cases of the same file existing 
under both both =-prefixed and non-prefixed names; when that happens, I
have to do a lot of hand-work to figure out what's actually going on,

The dead branches complicate this process a *lot*, esoecially the part
where I back up through the history looking for a ChangeLog entry marking
the actual deletion point.  I just figured out that the reason I've only
found two real deletion points in sixteen tries is because the dead
branches are getting in the way.

This makes me want to chop them all off.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>



  reply	other threads:[~2014-02-12  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 20:33 Should 'old-branches' and 'other-branches' be kept? Eric S. Raymond
2014-02-12  1:53 ` Stefan Monnier
2014-02-12  3:23   ` Eric S. Raymond [this message]
2014-02-12 14:01     ` Stefan Monnier
2014-02-12 14:30       ` Eric S. Raymond

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

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

  git send-email \
    --in-reply-to=20140212032344.GA20023@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.