updating git repositories fails for git version 1.6.5.3

Comments (11)

1. 

   Bruno Mundim

   • removed comment

   you can use git/1.7.4 module on Ranger.

   • 2011-10-11T18:21:03+00:00
2. 

   Roland Haas reporter

   • removed comment

   Indeed, good to know. The new version is even the default in the module system (1.6 is the one in /usr/bin). Also affects QueenBee where `soft add +git` provides git version 1.6.1.3

   • 2011-10-11T18:26:34+00:00
3. 

   Erik Schnetter

   • changed milestone to ET_2011_10
   • removed comment

   • 2011-10-12T07:37:49+00:00
4. 

   Roland Haas reporter

   • changed status to open
   • removed comment

   • 2011-10-18T18:50:06+00:00
5. 

   Ian Hinder

   • removed comment

   I think this should be included in the release, otherwise people with old versions of git won't be able to update. I am concerned about making assumptions about the human-readable output of git status, but I think we have to live with it. I propose committing this before the release. Any objections?

   • 2011-10-18T20:53:38+00:00
6. 

   Frank Löffler

   • removed comment

   Right. 'status' is a porcelain command, and according to the manual that is "not meant to be parsed" and "susceptible to changes/evolutions". For tasks like this the plumbing commands should be used. On the other hand, the manual for git-status on option --porcelain gives the opposite impression: "Give the output in a stable, easy-to-parse format for scripts. ... guaranteed not to change in the future, making it safe for scripts". It seems like git itself isn't quite consistent here.

   The current manpage for git-status lists '-s' as alternative. Ranger doesn't seem to be available for testing and queenbee doesn't seem to have a working git help. Maybe we could use this instead of --porcelain? But that's just an observation - I would be fine with the current patch.

   • 2011-10-18T21:37:13+00:00
7. 

   anonymous

   • removed comment

   I didn't know that git offered a stable interface. Very nice.

   --short does not exist either. This is on bethe (git 1.6.5.3):

   [rhaas@bethe CRL]$ git status --short error: unknown option `short' usage: git status [options] [--] <filepattern>...

   -q, --quiet be quiet -v, --verbose be verbose

   Commit message options -F, --file <FILE> read log from file --author <AUTHOR> override author for commit -m, --message <MESSAGE> specify commit message -c, --reedit-message <COMMIT> reuse and edit message from specified commit -C, --reuse-message <COMMIT> reuse message from specified commit -s, --signoff add Signed-off-by: -t, --template <FILE> use specified template file -e, --edit force edit of commit

   Commit contents options -a, --all commit all changed files -i, --include add specified files to index for commit --interactive interactively add files -o, --only commit only specified files -n, --no-verify bypass pre-commit hook --dry-run show what would be committed --amend amend previous commit -u, --untracked-files[=<mode>] show untracked files, optional modes: all, normal, no. (Default: all) --allow-empty ok to record an empty change --cleanup <default> how to strip spaces and #comments from message

   There is a discussion on this on stackoverflow: http://stackoverflow.com/questions/2657935/checking-for-a-dirty-index-or-untracked-files-with-git and point 26 seems to suggest to use

   git diff-files --quiet and to check its return value. That seems to work on bethe for me.

   • 2011-10-18T22:26:19+00:00
8. 

   Frank Löffler

   • removed comment

   Can you provide a patch - whoever was that 'anonymous'?

   • 2011-10-18T23:35:58+00:00
9. 

   Roland Haas reporter

   • removed comment

   I was anonymous (I didn't add an extra post for that, thought my userename in the pasted output might be a dead giveaway). Oh well :-)

   Patch is attached.

   • 2011-10-19T08:30:33+00:00
10. 

    Frank Löffler

    • changed status to resolved
    • removed comment

    Applied, thanks.

    • 2011-10-19T10:16:15+00:00
11. 

    Roland Haas reporter

    • edited description
    • changed status to closed

    • 2019-02-21T20:23:30+00:00
12. Log in to comment