All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Rudolf Polzer <divVerent@alientrap.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git push --track
Date: Wed, 13 Jan 2010 18:27:36 +0200	[thread overview]
Message-ID: <20100113162736.GA7505@Knoppix> (raw)
In-Reply-To: <op.u6haiiiog402ra@nb-04>

On Wed, Jan 13, 2010 at 04:55:20PM +0100, Rudolf Polzer wrote:
> On Wed, 13 Jan 2010 16:43:10 +0100, Ilari Liusvaara
> <ilari.liusvaara@elisanet.fi> wrote:
> 
> >On Wed, Jan 13, 2010 at 04:12:49PM +0100, Rudolf Polzer wrote:
> >>Hi,
> >>
> 
> Of course, but I assume the sign-off would not be by me, but by some
> of the git developers, and would depend on whether they actually
> want this feature.

It would need sign-off by you. Even if you took the code from somewhere
(and then it would need theirs as well) and passed it along.
 
> >- Should the tracking be set up even if only part of ref update suceeded
> >(for those that succeeded), not requiring all to succeed?
> 
> Good point, but I simply see no clean way to set it up for the
> succeeded refs. Would be a nice idea for improvement of this.

Ah, that is only known in transport_push and what it calls (and transport_push
is last point to insert common functionality)...
 
> @@ -218,6 +249,8 @@ int cmd_push(int argc, const char **argv, const
> char *prefix)
>  		OPT_BOOLEAN( 0 , "thin", &thin, "use thin pack"),
>  		OPT_STRING( 0 , "receive-pack", &receivepack, "receive-pack",
> "receive pack program"),
>  		OPT_STRING( 0 , "exec", &receivepack, "receive-pack", "receive
> pack program"),
> +		OPT_BIT('t', "track",  &flags, "set up tracking mode (see git-pull(1))",
> +			TRANSPORT_PUSH_TRACK),
>  		OPT_END()
>  	};

Linewrap damage.

-Ilari

  reply	other threads:[~2010-01-13 16:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 15:12 [PATCH] git push --track Rudolf Polzer
2010-01-13 15:43 ` Ilari Liusvaara
2010-01-13 15:55   ` Rudolf Polzer
2010-01-13 16:27     ` Ilari Liusvaara [this message]
2010-01-13 16:37     ` Matthieu Moy
2010-01-14  5:21     ` Tay Ray Chuan
2010-01-14  7:00       ` Rudolf Polzer
2010-01-14 23:13         ` Junio C Hamano
2010-01-14  7:16     ` Jeff King
2010-01-15  5:47     ` Junio C Hamano
2010-01-15 14:00       ` Rudolf Polzer
2010-01-15 15:45         ` Miles Bader
2010-01-15 18:16         ` Junio C Hamano
2010-01-14  0:28   ` Miles Bader
2010-01-14  0:25 ` Miles Bader
2010-01-14  0:33   ` Johannes Schindelin
2010-01-14  0:36     ` Miles Bader
2010-01-14  0:46   ` Miles Bader
2010-01-14  7:01   ` Rudolf Polzer
2010-01-14 13:44   ` Martin Langhoff
2010-01-14 14:16     ` Johannes Schindelin
2010-01-14 14:25       ` Matthieu Moy
2010-01-14 14:35         ` Martin Langhoff
2010-01-14 15:27         ` Andreas Krey
2010-01-14  1:27 ` Tay Ray Chuan
2010-01-14  1:35   ` Miles Bader
2010-01-14  1:37     ` Tay Ray Chuan
2010-01-14  1:49       ` Miles Bader
2010-01-14  1:58         ` Tay Ray Chuan
2010-01-14  7:03   ` Rudolf Polzer
2010-01-14 23:46     ` Junio C Hamano
2010-01-15  0:30       ` Miles Bader
2010-01-15 18:18         ` Junio C Hamano
2010-01-15 18:54           ` Miles Bader
2010-01-15 13:26       ` Matthieu Moy
2010-01-14  6:41 ` Nanako Shiraishi
2010-01-14  7:08   ` Rudolf Polzer
2010-01-14 10:31   ` Johannes Schindelin
2010-01-14 22:27     ` Nanako Shiraishi
2010-01-14 23:50       ` Junio C Hamano
2010-01-15 13:44       ` Rudolf Polzer
2010-01-15 14:09         ` Johannes Schindelin

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=20100113162736.GA7505@Knoppix \
    --to=ilari.liusvaara@elisanet.fi \
    --cc=divVerent@alientrap.org \
    --cc=git@vger.kernel.org \
    /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.