From: Marcin Owsiany <marcin@owsiany.pl>
To: Eric Wong <normalperson@yhbt.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFC] git-svn: don't create master if another head exists
Date: Wed, 18 Jul 2012 13:47:23 +0100 [thread overview]
Message-ID: <20120718124723.GA17379@beczulka> (raw)
In-Reply-To: <20120718112722.GA22042@dcvr.yhbt.net>
On Wed, Jul 18, 2012 at 11:27:22AM +0000, Eric Wong wrote:
> Marcin Owsiany <marcin@owsiany.pl> wrote:
> > On Wed, Jul 11, 2012 at 03:56:43PM -0700, Junio C Hamano wrote:
> > > If the caller does not handle errors, it could be even clearer to
> > > write it like
> > >
> > > command_noisy(qw(update-ref HEAD), $gs->refname) ||
> > > die "Cannot update HEAD!!!";
> >
> > Turns out that command_noisy()
> > - has a meaningless return value
> > - throws an exception on command failure
> > so the "||" bit does not work.
> > Also, for some reason command_noisy does not check for the command being
> > killed by a signal, so I'd prefer to leave the verify_ref there.
>
> Ugh, I always forget the Git.pm API, too. Perhaps command_noisy should
> be made to respect signals in exit codes (the rest of git-svn is
> compromised by this behavior in command_noisy, too, it turns out... :x)
>
> I'm not sure what else would break if command_noisy were changed,
> git-svn appears to be the only user in git.git.
Other "command" flavours should probably also be changed to match?
--
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-07-18 12:47 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
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 [this message]
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=20120718124723.GA17379@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 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.