git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] push: Alias pushurl from push rewrites

From
Rob Hoelz <rob@hoelz.ro>
Date
Mar 27, 2013, 17:20 UTC
Message-ID
<20130327122059.7e9da729@hoelz.ro>
In-Reply-To
<7vk3p2gmup.fsf@alter.siamese.dyndns.org>

On Wed, 20 Mar 2013 07:35:58 -0700 Junio C Hamano <gitster@pobox.com> wrote:

Show 39 quoted lines
> Rob Hoelz <rob@hoelz.ro> writes:
> 
> > On 3/19/13 7:08 PM, Junio C Hamano wrote:
> >> Jonathan Nieder <jrnieder@gmail.com> writes:
> >>
> >>> Junio C Hamano wrote:
> >>>> Jonathan Nieder <jrnieder@gmail.com> writes:
> >>>>> Test nits:
> >>>>> ...
> >>>>> Hope that helps,
> >>>>>
> >>>>> Jonathan Nieder (3):
> >>>>>   push test: use test_config where appropriate
> >>>>>   push test: simplify check of push result
> >>>>>   push test: rely on &&-chaining instead of 'if bad; then echo
> >>>>> Oops; fi'
> >>>> Are these supposed to be follow-up patches?  Preparatory steps
> >>>> that Rob can reroll on top?  Something else?
> >>> Preparatory steps.
> >> OK, thanks.  I'll queue these first then.
> >>
> > Should I apply these to my patch to move things along?  What's the
> > next step for me?
> 
> You would fetch from nearby git.git mirror, find the tip of
> Janathan's series and redo your patch on top.  Perhaps the session
> would go like this:
> 
>     $ git fetch git://git.kernel.org/pub/scm/git/git.git/ pu
>     $ git log --oneline --first-parent ..FETCH_HEAD | grep
> jn/push-tests 83a072a Merge branch 'jn/push-tests' into pu
>     $ git checkout -b rh/push-pushurl-pushinsteadof 83a072a
>     ... redo the work, perhaps with combinations of:
>     $ git cherry-pick -n $your_original_branch
>     $ edit t/t5516-fetch-push.sh
>     ... and then
>     $ make test
>     $ git commit
> 
Ok, changes applied.  New patch coming.
Previous: Junio C Hamano
Message 11 of 11 in “push: Alias pushurl from push rewrites”
  1. push: Alias pushurl from push rewritesRob Hoelz, Mar 18, 2013
  2. Jonathan NiederMar 18, 2013
  3. 1/3 push test: use test_config when appropriateJonathan Nieder, Mar 18, 2013
  4. 2/3 push test: simplify check of push resultJonathan Nieder, Mar 18, 2013
  5. 3/3 push test: rely on &&-chaining instead of 'if bad; then echo Oops; fi'Jonathan Nieder, Mar 18, 2013
  6. Junio C HamanoMar 19, 2013
  7. Jonathan NiederMar 19, 2013
  8. Junio C HamanoMar 19, 2013
  9. Rob HoelzMar 20, 2013
  10. Junio C HamanoMar 20, 2013
  11. Rob HoelzMar 27, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.