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

Re: What's cooking in git.git (Apr 2014, #08; Fri, 25)

From
Jeff King <peff@peff.net>
Date
Apr 26, 2014, 04:25 UTC
Message-ID
<20140426042521.GA5799@sigill.intra.peff.net>
In-Reply-To
<535b0db7e5e31_ba2148d310f4@nysa.notmuch>
On Fri, Apr 25, 2014 at 08:36:55PM -0500, Felipe Contreras wrote:
Show 9 quoted lines
> > As for the patches themselves, I have not reviewed them carefully, and
> > would prefer not to. As I mentioned before, though, I would prefer the
> > short "@{p}" not be taken for @{publish} until it has proven itself.
> 
> Presumably you want to save it for @{push}. While I'm not against to having
> just @{publish} for now, I'm farily certain most people would be using
> @{publish} and not @{push}, as that's what `git branch -v` would show, and it
> would be closely similar to @{upstream}. Therefore it would make sense to use
> @{p} for @{publish}

No, I do not think it would be a good idea for @{push}, either. If we have two concepts so similarly named (and especially if we add @{pull}, which has also been mentioned), then I think having @{p} just adds to confusion. So I would much rather wait and see. It is very easy to add @{p} later, but it is very hard to take it back once used.

-Peff
Previous: Felipe ContrerasNext: Junio C Hamano
Message 8 of 14 in “What's cooking in git.git (Apr 2014, #08; Fri, 25)”
  1. Junio C HamanoApr 25, 2014
  2. Jeff KingApr 25, 2014
  3. Felipe ContrerasApr 26, 2014
  4. Alex DavidsonApr 26, 2014
  5. Felipe ContrerasApr 26, 2014
  6. Philip OakleyApr 26, 2014
  7. Felipe ContrerasApr 26, 2014
  8. Jeff KingApr 26, 2014
  9. Junio C HamanoApr 28, 2014
  10. Jeff KingApr 28, 2014
  11. Michael HaggertyMay 9, 2014
  12. Felipe ContrerasMay 9, 2014
  13. Philip OakleyMay 9, 2014
  14. Jeff KingMay 12, 2014

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.