From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Sven Strickroth <sven.strickroth@tu-clausthal.de>
Cc: git@vger.kernel.org
Subject: Re: RFC: reflog for deleted branches
Date: Thu, 03 May 2012 23:13:16 +0100 [thread overview]
Message-ID: <4FA302FC.2040608@pileofstuff.org> (raw)
In-Reply-To: <4FA2F7DA.6020108@tu-clausthal.de>
On 03/05/12 22:25, Sven Strickroth wrote:
> Hi,
>
> an often heart question is how to restore deleted branches. Sometimes
> those can be restored by using the reflog of the HEAD.
>
> But why not create a special (ref)log for deleted branches (with SHA1,
> date, name of the branch and maybe commit message of the last commit on
> the deleted branch)? This way people could just look up the SHA1 of the
> deleted branch and can recreate it (even if they moved the HEAD around a
> lot).
>
Something like this may well be needed by an SVN importer, as it's quite
possible for an SVN branch to be deleted, then another branch forked
from it years later. See the (brief) discussion here:
http://article.gmane.org/gmane.comp.version-control.git/195517
http://article.gmane.org/gmane.comp.version-control.git/195544
This is really Florian's area, but I expect it would be easy enough for
SVN import to build on top of any reasonably general solution if you're
offering :)
- Andrew
next prev parent reply other threads:[~2012-05-03 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 21:25 RFC: reflog for deleted branches Sven Strickroth
2012-05-03 21:37 ` Junio C Hamano
2012-05-03 22:10 ` Sven Strickroth
2012-05-03 23:05 ` Junio C Hamano
2012-05-03 23:39 ` Sven Strickroth
2012-05-04 6:27 ` Robin Rosenberg
2012-05-04 16:24 ` Junio C Hamano
2012-05-03 22:13 ` Andrew Sayers [this message]
2012-05-04 1:17 ` Sitaram Chamarty
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=4FA302FC.2040608@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=git@vger.kernel.org \
--cc=sven.strickroth@tu-clausthal.de \
/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.
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 NNTP newsgroup(s).