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

Re: git bug/feature request

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 27, 2007, 11:30 UTC
Message-ID
<figv47$926$1@ger.gmane.org>
In-Reply-To
<200711271127.41161.gapon007@gmail.com>
gapon wrote:
> hi all,
> first of all i don't know if there's a bugzilla or something similar
> for git - i have found just this email (on http://git.or.cz/ webpage).

There isn't any bug tracker for git. Use git mailing list for bug reports and feature requests.

> i have discovered "weird" behaviour of git in this scenario*:
> - user A is working in repo A
> - user B clones repo A
> - user B makes some changes, commits, pushes
Do not push into checked out branch!
Show 8 quoted lines
> - user A makes some changes, git status (no info about new commit
>   in his repo from user B but it's probably ok i'd say - but some
>   of my files are marked as changed and already added to index
>   but i haven't changed them - that's confusing, isn't it?)
> - user A can commit his changes => shouldn't be there any
>   info/message/warning displayed? it would be helpful to have
>   here some info about "foreign commit" in the repo or something
>   like this 

Perhaps there should. There was some idea and even preliminary implementation of BASE check, but IIRC it was deemed too complicated, and encouraging wrong workflow.

Besides, even with the check, pushing into checked out branch can quite easily lead either to loosing (or at least vanishing) some history, or problems with pushing.

> * yes, i know that this scenario is "incorrect" but... it's possible and 
>   therefore i think it should be somehow handled - i tried a similar one
>   with hg and bzr and i like their behaviour more

IIRC we strongly discourage in documentation to push into checked out branch. Either use bare repository for communication (it allows for example for got for "ideal patch series" by rewriting history _before publishing (pushing)_ and for communication with more than one chosen developer), or push into _remotes_, not into heads.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Alex RiesenNext: Jan Hudec
Message 14 of 22 in “git bug/feature request”
  1. gaponNov 27, 2007
  2. Benoit SigoureNov 27, 2007
  3. gaponNov 27, 2007
  4. Jakub NarebskiNov 27, 2007
  5. gaponNov 27, 2007
  6. Jakub NarebskiNov 27, 2007
  7. Jakub NarebskiNov 27, 2007
  8. gaponNov 27, 2007
  9. Alex RiesenNov 27, 2007
  10. gaponNov 27, 2007
  11. Alex RiesenNov 27, 2007
  12. gaponNov 27, 2007
  13. Alex RiesenNov 27, 2007
  14. Jakub NarebskiNov 27, 2007
  15. Jan HudecNov 30, 2007
  16. Peter KarlssonNov 27, 2007
  17. David KastrupNov 27, 2007
  18. Peter KarlssonNov 28, 2007
  19. Jakub NarebskiNov 27, 2007
  20. Steven GrimmNov 27, 2007
  21. Daniel BarkalowNov 27, 2007
  22. Daniel BarkalowNov 27, 2007

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.