From: Andy Whitcroft <apw@shadowen.org>
To: Lars Hjemli <hjemli@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [RFC] git-branch: add options and tests for branch renaming
Date: Tue, 28 Nov 2006 15:03:42 +0000 [thread overview]
Message-ID: <456C4FCE.6090306@shadowen.org> (raw)
In-Reply-To: <11647252603530-git-send-email-hjemli@gmail.com>
Lars Hjemli wrote:
> Extend git-branch with the following options:
>
> git-branch -m|-M [<oldbranch>] newbranch
>
> The -M variation is required to force renaming over an exsisting
> branchname.
>
> This also indroduces $GIT_DIR/RENAME_REF which is a "metabranch"
> used when renaming branches. It will always hold the original sha1
> for the latest renamed branch.
>
> Additionally, if $GIT_DIR/logs/RENAME_REF exists, all branch rename
> events are logged there.
>
> Finally, some testcases are added to verify the new options.
Ok, I have been feeling uneasy about rename and reflogs for a while now.
About removing reflogs too for that matter.
In my mind the ref log is about tracking what a ref points to. So I
want to be able to say "what was next, yesterday". Do I care if its not
there now? Perhaps I want a rename to just put a rename from in the top
of the new reflog and leave the old there.
Yep, no idea how we would clean them up with this model. But ...
next prev parent reply other threads:[~2006-11-28 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 14:47 [RFC] git-branch: add options and tests for branch renaming Lars Hjemli
2006-11-28 15:03 ` Andy Whitcroft [this message]
2006-11-28 15:39 ` Shawn Pearce
2006-11-28 16:10 ` Lars Hjemli
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=456C4FCE.6090306@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
--cc=junkio@cox.net \
/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).