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

Re: [RFC/PATCH] git put: an alternative to add/reset/checkout

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 23, 2012, 18:10 UTC
Message-ID
<7vaa5e9tn2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CADo4Y9j5MwKr+rWza0ncLWuthY6x+s68CQYbY2+c8-E5pAa=Sw@mail.gmail.com>
Michael Nahas <mike.nahas@gmail.com> writes:
> It obviously isn't the design-first-then-find-a-willing-programmer of
> the project I ran. I don't know if it's the IETF's "running code and
> a general consensus".
These two are not necessarily incompatible.

A proposed new feature needs to be explained well, describing in what situation it will help what kind of users and without hurting others and why it is a worthy addition.

We require a general consensus that any proposed change is a worthy addition, and a working code is often a good addition to help us reaching one, because people can guess what is being proposed even when the idea is presented poorly. A poorly presented idea without working code often fares no better than just a handwaving with crazy talk, as you fail to make others realize what you are trying to achieve.

But working code is not a requirement to present good ideas. It just helps to add clarity to it.

Previous: Michael Nahas
Message 18 of 18 in “git put: an alternative to add/reset/checkout”
  1. git put: an alternative to add/reset/checkoutJeff King, Jun 7, 2011
  2. Junio C HamanoJun 7, 2011
  3. Jeff KingJun 7, 2011
  4. Michael NahasJun 8, 2011
  5. Jakub NarebskiJun 8, 2011
  6. Matthieu MoyJun 8, 2011
  7. Jeff KingJun 8, 2011
  8. Matthieu MoyJun 8, 2011
  9. Jakub NarebskiJun 8, 2011
  10. Matthieu MoyJun 8, 2011
  11. Jakub NarebskiJun 8, 2011
  12. Nguyen Thai Ngoc DuyJun 10, 2011
  13. Nguyen Thai Ngoc DuyJun 8, 2011
  14. Nguyen Thai Ngoc DuyJan 23, 2012
  15. Michael NahasJan 23, 2012
  16. Nguyen Thai Ngoc DuyJan 23, 2012
  17. Michael NahasJan 23, 2012
  18. Junio C HamanoJan 23, 2012

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.