From: Marcin Owsiany <marcin@owsiany.pl>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH/RFC] git-svn: don't create master if another head exists
Date: Tue, 26 Jun 2012 22:21:08 +0100 [thread overview]
Message-ID: <20120626212108.GR3125@beczulka> (raw)
In-Reply-To: <7vehp3gwbx.fsf@alter.siamese.dyndns.org>
On Mon, Jun 25, 2012 at 10:01:06AM -0700, Junio C Hamano wrote:
> Marcin Owsiany <marcin@owsiany.pl> writes:
>
> >> What are you really trying
> >> to validate? "HEAD" points at an existing branch and you do not
> >> care what branch it is?
> >
> > Yes. I think.
>
> Why do you even care about the value of HEAD, i.e. the output from
> "rev-parse HEAD", if that is the case?
I don't!
> Wouldn't you rather be
> reading from the output "symbolic-ref HEAD" to see if it points at
> any branch?
Sure, I was simply not aware of its existence.
However after actually trying this approach I have found out that when
post_fetch_checkout runs at initial "clone", HEAD points at
refs/heads/master, but refs/heads/master does not exist! So just
checking HEAD is not enough, I need to verify that it points to
something valid. How about this:
From: Marcin Owsiany <marcin@owsiany.pl>
Date: Sun, 24 Jun 2012 22:40:05 +0100
Subject: [PATCH] git-svn: don't create master if another head exists
git-svn insists on creating the "master" head (unless it exists) on every
"fetch". While it is useful that it gets created initially (users expect this
git convention), some users find it annoying that it gets recreated, especially
when they would like the git branch names to follow SVN repository branch
names. More background in
http://thread.gmane.org/gmane.comp.version-control.git/115030
Make git-svn skip the "master" creation if HEAD points at a valid head. This
means "master" does get created on initial "clone" but does not get recreated
once a user deletes it.
Signed-off-by: Marcin Owsiany <marcin@owsiany.pl>
---
git-svn.perl | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index 0b074c4..2379a71 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -1612,9 +1612,9 @@ sub post_fetch_checkout {
}
}
- my $valid_head = verify_ref('HEAD^0');
+ return if verify_ref('HEAD^0');
command_noisy(qw(update-ref refs/heads/master), $gs->refname);
- return if ($valid_head || !verify_ref('HEAD^0'));
+ return unless verify_ref('HEAD^0');
return if $ENV{GIT_DIR} !~ m#^(?:.*/)?\.git$#;
my $index = $ENV{GIT_INDEX_FILE} || "$ENV{GIT_DIR}/index";
--
1.7.7.3
--
Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/
GnuPG: 2048R/02F946FC 35E9 1344 9F77 5F43 13DD 6423 DBF4 80C6 02F9 46FC
"Every program in development at MIT expands until it can read mail."
-- Unknown
next prev parent reply other threads:[~2012-06-26 21:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 22:08 [PATCH/RFC] git-svn: don't create master if another head exists Marcin Owsiany
2012-06-25 4:16 ` Eric Wong
2012-06-25 6:01 ` Junio C Hamano
2012-06-25 7:41 ` Marcin Owsiany
2012-06-25 5:44 ` Junio C Hamano
2012-06-25 7:53 ` Marcin Owsiany
2012-06-25 5:47 ` Junio C Hamano
2012-06-25 7:57 ` Marcin Owsiany
2012-06-25 17:01 ` Junio C Hamano
2012-06-26 21:21 ` Marcin Owsiany [this message]
2012-06-26 22:03 ` Junio C Hamano
2012-06-26 22:32 ` Marcin Owsiany
2012-07-09 22:03 ` Marcin Owsiany
2012-07-09 22:43 ` Junio C Hamano
2012-07-11 1:26 ` Eric Wong
2012-07-11 21:40 ` Marcin Owsiany
2012-07-11 22:56 ` Junio C Hamano
2012-07-18 7:49 ` Marcin Owsiany
2012-07-18 11:27 ` Eric Wong
2012-07-18 12:47 ` Marcin Owsiany
2012-07-19 8:19 ` Eric Wong
2012-07-19 17:20 ` Junio C Hamano
2012-07-18 20:32 ` Junio C Hamano
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=20120626212108.GR3125@beczulka \
--to=marcin@owsiany.pl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.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).