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

Re: [PATCH] git-commit: revamp the git-commit semantics.

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Feb 5, 2006, 13:36 UTC
Message-ID
<e5bfff550602050536j73f1091dq9afae232f574d0b4@mail.gmail.com>
In-Reply-To
<7vpsm2hzng.fsf@assigned-by-dhcp.cox.net>
On 2/5/06, Junio C Hamano <junkio@cox.net> wrote:
Show 8 quoted lines
> I am addressing people who participated with their valuable
> inputs to the earlier "git commit" discussion.
>
> Here is my first cut.  I'd appreciate to hear from both
> git-experienced people and git newcomers how comfortable this
> new implementation is.  Improvement patches on top of this are
> certainly appreciated.
>

I think the new semantics is clear and better then old one, especially for people coming from different scm systems.

Unfortunately it breaks qgit commit functionality. So I would like to ask _how_ do you plan to update main line.

I would like to update qgit also today, but it is impossible because "git-commit -i" _currently_ raises an error. So I am just wondering if adding a temporary -i "no op" option to _current_ git-commit, until semantics change is released could be done.

Adding a -i "place holder" option to _current_ git-commit has the following advantages:

1) No functionality change and 100%  compatibility with current git-commit use.
2) Give people time to update tools/script in the mean time
3) When the real patch will be released all the (modified) tools will
be automatically compatible.
What do you think?
Marco
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 16 in “git-commit: revamp the git-commit semantics.”
  1. git-commit: revamp the git-commit semantics.Junio C Hamano, Feb 5, 2006
  2. Marco CostalbaFeb 5, 2006
  3. Junio C HamanoFeb 5, 2006
  4. Marco CostalbaFeb 5, 2006
  5. Junio C HamanoFeb 5, 2006
  6. Nicolas PitreFeb 7, 2006
  7. Junio C HamanoFeb 7, 2006
  8. Junio C HamanoFeb 7, 2006
  9. Jon LoeligerFeb 7, 2006
  10. Nicolas PitreFeb 7, 2006
  11. Nicolas PitreFeb 7, 2006
  12. Junio C HamanoFeb 8, 2006
  13. Junio C HamanoFeb 6, 2006
  14. Junio C HamanoFeb 6, 2006
  15. Michael FischerFeb 6, 2006
  16. Junio C HamanoFeb 6, 2006

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.