From: Marcin Owsiany <marcin@owsiany.pl>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Dmitry Potapov <dpotapov@gmail.com>,
git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: git-svn stubbornly re-creating branch "master"
Date: Sat, 6 Jun 2009 11:55:01 +0100 [thread overview]
Message-ID: <20090606105501.GA29758@beczulka> (raw)
In-Reply-To: <237967ef0904030357u15ef77f2rb3299b6f6c651404@mail.gmail.com>
This discussion seems to have stalled...
On Fri, Apr 03, 2009 at 12:57:52PM +0200, Mikael Magnusson wrote:
> 2009/3/29 Dmitry Potapov <dpotapov@gmail.com>:
> > On Sun, Mar 29, 2009 at 18:13:47 +0100, Marcin Owsiany
> > <porridge@debian.org> wrote:
> >>
> >> As you can see, "master" sprang back to life after the last command.
> >
> > It looks like git-svn does not like a repo without 'master'. It seems
> > the problem was caused by this patch:
> > http://git.kernel.org/?p=git/git.git;a=commit;h=1e889ef36c45b5554f7e317493ed3f4f901f8d9f
> >
> > I have added Eric to CC...
>
> Why not just check if HEAD points to a valid commit, rather than
> master? It should do the same
> in the newly created repo case, and stop annoying people on updates.
There seems to be agreement that while conventions are nice, git should
not force branch names on people. Can someone implement Mikael's
suggestion?
--
Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216
"Every program in development at MIT expands until it can read mail."
-- Unknown
next prev parent reply other threads:[~2009-06-06 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 17:13 git-svn stubbornly re-creating branch "master" Marcin Owsiany
2009-03-29 19:52 ` Dmitry Potapov
2009-04-03 10:57 ` Mikael Magnusson
2009-06-06 10:55 ` Marcin Owsiany [this message]
2009-06-14 15:52 ` Marcin Owsiany
2009-06-14 17:33 ` Andreas Ericsson
2009-06-14 21:16 ` Marcin Owsiany
2009-03-29 22:28 ` Eric Wong
2009-04-03 10:42 ` David Kågedal
2009-04-03 12:26 ` Marcin Owsiany
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=20090606105501.GA29758@beczulka \
--to=marcin@owsiany.pl \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=mikachu@gmail.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).