[PATCH v2 0/1] DiffHighlight.pm: Use correct /dev/null for UNIX and Windows

Use File::Spec->devnull() for output redirection to avoid messages when Windows version of Perl is first in path. The message 'The system cannot find the path specified.' is displayed each time git is run to get colors. Chris. Webster (1): diff-highlight: Use correct /dev/null for U

Re: [PATCH 1/1] Use correct /dev/null for UNIX and Windows

Resending in text mode. On Tue, Oct 30, 2018 at 10:20 PM Chris Webster wrote: > > On Tue, Oct 30, 2018 at 9:54 PM Junio C Hamano wrote: >> >> "chris via GitGitGadget" writes: >> >> > From: chris >> > >> > Use File::Spec->devn

[PATCH 0/1] DiffHighlight.pm: Use correct /dev/null for UNIX and Windows

Use File::Spec->devnull() for output redirection to avoid messages when Windows version of Perl is first in path. The message 'The system cannot find the path specified.' is displayed each time git is run to get colors. chris (1): Use correct /dev/null for UNIX and Windows contrib/d

[PATCH 1/1] Use correct /dev/null for UNIX and Windows

From: chris Use File::Spec->devnull() for output redirection to avoid messages when Windows version of Perl is first in path. The message 'The system cannot find the path specified.' is displayed each time git is run to get colors. Signed-off-by: Chris. Webster --- contrib/diff-highli

Re: inside the git folder

: > > On Wed, Oct 3, 2018 at 5:26 AM Chris Jeschke > wrote: > > > > Hey git-team, > > I am working on a plug-in for a distributed pair programming tool. To > > skip the details: I was thinking about sending parts of the git folder > > as a zip folder w

inside the git folder

Hey git-team, I am working on a plug-in for a distributed pair programming tool. To skip the details: I was thinking about sending parts of the git folder as a zip folder with our own Bytestream instead of using the git API. Is there a common sense about what should and what shouldn't be done when

Re: Question - no space in smtp-server-option

On Sep-16-18, Jonathan Nieder wrote: On Mon, Sep 17, 2018 at 03:27:21AM +0200, Chris Coutinho wrote: On Sep-16-18, Jonathan Nieder wrote: Chris Coutinho wrote: Currently my gitconfig contains the following line: sendemail.smtpserveroption=-a Whereas, the following results

Re: Question - no space in smtp-server-option

On Sep-16-18, Jonathan Nieder wrote: On Mon, Sep 17, 2018 at 03:27:21AM +0200, Chris Coutinho wrote: On Sep-16-18, Jonathan Nieder wrote: Chris Coutinho wrote: Currently my gitconfig contains the following line: sendemail.smtpserveroption=-a Whereas, the following results

Re: Question - no space in smtp-server-option

On Sep-16-18, Jonathan Nieder wrote: Hi, Chris Coutinho wrote: Currently my gitconfig contains the following line: sendemail.smtpserveroption=-a Whereas, the following results in an 'account' not found error: sendemail.smtpserveroption=-a Do you mean that your

Question - no space in smtp-server-option

this? Regards, Chris signature.asc Description: PGP signature

ACKNOWLEDGE MY MAIL (Mutual Benefit)

. .. I will hope for your co-operation. Sincerely Yours, Chris Brown.

Re: git push => git: 'credential-winstore' is not a git command.

Thanks, Peff. I should have thought about the configuration hierarchy... This evening I need to do some trial-and-error with the three credential entries that found. Want what you have, Chris On Wed, May 23, 2018 at 1:16 AM, Jeff King <p...@peff.net> wrote: > On Sun, May 20, 2018 at 1

git push => git: 'credential-winstore' is not a git command.

al symptom of a larger problem)? Thanks, Chris

Re: git-gui ignores core.hooksPath

will pick up this / these changes? Will anyone else be assigned the main responsible for this git-gui repository? Just hoping to revive the discussion here, since the https://github.com/patthoyts/git-gui/ repository seems quite dead. sincerely, Chris Maes. -- Macq nv Luchtschipstraat, 2 - 1140

Donation of £1,500,000.00 GBP!!

My wife and I have awarded you with a donation of £1,500,000.00 GBP from part of our Jackpot Lottery of £161,653,000 Million Pounds, send your name,address, phone for claims. We await your earliest response and God Bless you. Best of luck. Chris Colin & Weir

Re: [PATCH] enable core.fsyncObjectFiles by default

On 01/18/2018 11:27 AM, Christoph Hellwig wrote: [adding Chris to the Cc list - this is about the awful ext3 data=ordered behavior of syncing the whole file system data and metadata on each fsync] On Wed, Jan 17, 2018 at 03:57:53PM -0800, Linus Torvalds wrote: On Wed, Jan 17, 2018 at 3:52 PM

Re: [SCRIPT/RFC 0/3] git-commit --onto-parent (three-way merge, no working tree file changes)

On Nov 27, 2017, at 00:35, Igor Djordjevic wrote: > Approach discussed here could have a few more useful applications, > but one seems to be standing out the most - in case where multiple > topic branches are temporarily merged for integration testing, it > could

[buglet] gitk and git cherry-pick --abort interaction

{33} are rebase/commit/am/cherry-pick d2b10042ccaf (HEAD -> edac) HEAD@{34}: am --abort Thanks, Chris

Hello:

Greetings, I'm Chris Rholand Esq, from DLA (Defence League of Attorneys) & Associates, London, United Kingdom, We are attorneys to your deceased relative, Who leaved in London. You have the right to his inheritance as next of kin. Reply ASAP for more details on how to proceed, Sincerely, C

die("bad object.. for duplicate tagged tag in remote

ith this meaningless error. The attached patch improves the error. I don't know where the rest of the problem lies. What's the expected behaviour when a tag already exists locally, but is different? Fetch the object anyway, but ignore it? >From aa861789077012f78605431e1a1f191292693325 Mon Sep

Re: Bug Report: .gitignore behavior is not matching in git clean and git status

-all here, but will a reply automatically include the rest of the list? Or was reply-all the right move? On Sun, Apr 30, 2017 at 9:41 PM, Junio C Hamano <gits...@pobox.com> wrote: > Chris Johnson <chrisjohns...@gmail.com> writes: > >> I am a mailing list noob so I’m sorry if

Bug Report: .gitignore behavior is not matching in git clean and git status

r as ignored files go. As it is, git status does NOT report A/B/C as an untracked file, but git clean will remove the entire A dir. It seems to me that one or the other’s behavior ought to be tweaked. Which one is correct I am not sure. This happens on 2.5.1 as well as 2.9.2 Chris

Re: git with ssh won't pull submodule

Hi Erik, On Fri, Apr 28, 2017 at 11:25 AM, Erik Haller wrote: > Getting the following error for a submodule when using git/ssh: > > $ git clone --recursive ssh://incense:/home/erik/git/nacl.git > Cloning into 'nacl'... > remote: Counting objects: 32, done. > remote:

Re: [Bug] Unicode display

Hi, On Wed, Mar 15, 2017 at 5:51 PM, Dũng Đặng Minh wrote: > Hi Git team, > > Thank you all for create a great tool. > Last week, I updated the last version of git (2.12.0 x64-Windows) and > all Unicode characters are display un-correctly. You can see: >

Re: Suggestion for the "Did you mean this?" feature

On Mon, Dec 19, 2016 at 1:18 AM, Kaartic Sivaraam wrote: > Hello all, > > I have found the "Did you mean this?" feature of git as a very good > feature. I thought it would be even better if it took a step toward by > asking for a prompt when there was only one

Re: [RFC/PATCHv2] Makefile: add cppcheck target

On Fri, Dec 16, 2016 at 9:28 PM, Lars Schneider <larsxschnei...@gmail.com> wrote: > > On 14 Dec 2016, at 12:24, Jeff King <p...@peff.net> wrote: > > On Wed, Dec 14, 2016 at 10:27:31PM +1300, Chris Packham wrote: > > Changes in v2: > > - only run over actual gi

[RFC/PATCH] Makefile: suppress some cppcheck false-positives

Pass a list of suppressions to cppcheck so that legitimate errors are more obvious. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- On Thu, Dec 15, 2016 at 12:24 AM, Jeff King <p...@peff.net> wrote: > The patch itself is OK to me, I guess. The interesting part will be &

Re: [PATCHv3 1/3] merge: Add '--continue' option as a synonym for 'git commit'

On Thu, Dec 15, 2016 at 7:04 AM, Junio C Hamano wrote: > The last one 3/3 is a nice touch that makes sure that we do not > forget what we discovered during the discussion. Very much > appreciated. > > Will queue. Thanks. Did you want me to send a v4 to mark the strings for

[RFC/PATCHv2] Makefile: add cppcheck target

be enabled by specifying CPPCHECK_ADD. This is a comma separated list which is passed to cppcheck's --enable option. To enable style and warning checks run make cppcheck CPPCHECK_ADD=style,warning Based-on-patch-by: Elia Pinto <gitter.spi...@gmail.com> Signed-off-by: Chris Packham <j

[PATCH 3/3] merge: Ensure '--abort' option takes no arguments

Like '--continue', the '--abort' option doesn't make any sense with other options or arguments to 'git merge' so ensure that none are present. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- Changes in v3: - new builtin/merge.c | 4 t/t7600-merge.sh | 2 ++ 2 files chan

[PATCHv3 1/3] merge: Add '--continue' option as a synonym for 'git commit'

to 'git merge' presents a consistent UI. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- Changes in v2: - add --continue to builtin_merge_usage - verify that no other arguments are present when --continue is used. - add basic test Changes in v3: - check for other options in a

[PATCH 2/3] completion: add --continue option for merge

Add 'git merge --continue' option when completing. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- Changes in v2: - new Changes in v3: - none contrib/completion/git-completion.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/completi

Re: [RFC/PATCH] Makefile: add cppcheck target

On Wed, Dec 14, 2016 at 1:15 AM, Jeff King <p...@peff.net> wrote: > On Tue, Dec 13, 2016 at 10:22:25PM +1300, Chris Packham wrote: > >> $ make cppcheck >> cppcheck --force --quiet --inline-suppr . >> [compat/nedmalloc/malloc.c.h:4093]: (error) Possible null pointer

Re: [RFC/PATCH] Makefile: add cppcheck target

On Wed, Dec 14, 2016 at 1:28 AM, Jeff King wrote: > On Tue, Dec 13, 2016 at 07:15:10AM -0500, Jeff King wrote: > >> I think these last two are a good sign that we need to be feeding the >> list of source files to cppcheck. I tried your patch and it also started >> looking in

Re: [RFC/PATCH] Makefile: add cppcheck target

On Tue, Dec 13, 2016 at 10:22 PM, Chris Packham <judge.pack...@gmail.com> wrote: > Add cppcheck target to Makefile. Cppcheck is a static > analysis tool for C/C++ code. Cppcheck primarily detects > the types of bugs that the compilers normally do not detect. > It is an useful t

[RFC/PATCH] Makefile: add cppcheck target

Add cppcheck target to Makefile. Cppcheck is a static analysis tool for C/C++ code. Cppcheck primarily detects the types of bugs that the compilers normally do not detect. It is an useful target for doing QA analysis. Based-on-patch-by: Elia Pinto <gitter.spi...@gmail.com> Signed-off-by:

[PATCHv2 1/2] merge: Add '--continue' option as a synonym for 'git commit'

to 'git merge' presents a consistent UI. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- Notes: Changes in v2: - add --continue to builtin_merge_usage - verify that no other arguments are present when --continue is used. - add basic test Documentation/git-merge.tx

[PATCHv2 2/2] completion: add --continue option for merge

Add 'git merge --continue' option when completing. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- Notes: Changes in v2: - new. contrib/completion/git-completion.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/completion/git-completio

Re: [RFC/PATCH] merge: Add '--continue' option as a synonym for 'git commit'

On Mon, Dec 12, 2016 at 10:02 PM, Markus Hitter <m...@jump-ing.de> wrote: > Am 12.12.2016 um 09:34 schrieb Chris Packham: >> Teach 'git merge' the --continue option which allows 'continuing' a >> merge by completing it. The traditional way of completing a merge after &

[RFC/PATCH] merge: Add '--continue' option as a synonym for 'git commit'

to 'git merge' presents a consistent UI. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- So here is a quick patch that adds the --continue option. I need to add some tests (suggestions for where to start are welcome). Documentation/git-merge.txt | 13 - builtin/m

Re: Any interest in 'git merge --continue' as a command

On Sat, Dec 10, 2016 at 8:16 AM, Junio C Hamano wrote: > Jeff King writes: > >>> They knew about git rebase --continue (and git am and git cherry-pick) >>> but they were unsure how to "continue" a merge (it didn't help that >>> the advice saying to use 'git

Any interest in 'git merge --continue' as a command

I hit this at $dayjob recently. A developer had got themselves into a confused state when needing to resolve a merge conflict. They knew about git rebase --continue (and git am and git cherry-pick) but they were unsure how to "continue" a merge (it didn't help that the advice saying to use 'git

Re: Bug in git rev-parse @{push}?

Will do, thanks! Meanwhile, I'll work around locally by changing off 'simple' in my config—if I can figure out how not to break everything in the process... On 3 November 2016 at 16:07, Jeff King <p...@peff.net> wrote: > On Thu, Nov 03, 2016 at 03:59:13PM +0000, Chris Purc

Re: Bug in git rev-parse @{push}?

>> Thanks, Jeff! If I remove the explicit configuration of remote.pushdefault >> = "origin", I get the same error message as you, so I suspect that's _not_ >> the default. > > That's really bizarre, because I get the same behavior with or without > it set. Not only that, but it shouldn't even come

Re: Bug in git rev-parse @{push}?

Resending to mailing list because Inbox is fighting with vger... On 3 November 2016 at 15:48, Chris Purcell <chris.purcell...@gmail.com> wrote: > Thanks, Jeff! If I remove the explicit configuration of remote.pushdefault = > "origin", I get the same error message as you, so

Bug in git rev-parse @{push}?

mportant information by mistake. I'm happy to work on a patch if given guidance, but this is definitely outside my comfort zone for an unfamiliar codebase otherwise! e.g. I can't find the test suite. Cheers, Chris

Repeatable Extraction

. For example, if I extract twice using PortableGit-2.10.0-32-bit.7z.exe -y -gm2 then Beyond Compare tells me that many of the files in usr\bin have changed at offset 0x88 and 0x89. Why is that? Warm regards, Chris

h

Sent from my iPhone

[RFC PATCH] completion: support excluding refs

Allow completion of refs with a ^ prefix. This allows completion of commands like 'git log HEAD ^origin/master'. Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- I often find myself using variations of 'git log HEAD ^origin/master' to see commits that I have locally that have no

Re: [RFC/PATCH] rebase--interactive: Add "sign" command

On Thu, Aug 4, 2016 at 6:08 AM, Jeff King wrote: > On Wed, Aug 03, 2016 at 09:08:48AM -0700, Junio C Hamano wrote: > >> > However, I could imagine that we actually want this to be more extensible. >> > After all, all you are doing is to introduce a new rebase -i command that >> >

Re: [RFC/PATCH] rebase--interactive: Add "sign" command

On Thu, Aug 4, 2016 at 2:31 AM, Johannes Schindelin <johannes.schinde...@gmx.de> wrote: > Hi Chris, > > On Wed, 3 Aug 2016, Chris Packham wrote: > >> This is similar to the existing "reword" command in that it can be used >> to update the commit message the

[RFC/PATCH] rebase--interactive: Add "sign" command

This is similar to the existing "reword" command in that it can be used to update the commit message the difference is that the editor presented to the user for the commit. It provides a useful shorthand for "exec git commit --amend --no-edit -s" Signed-off-by: Chris

[PATCHv1] completion: add option '--recurse-submodules' to 'git clone'

Signed-off-by: Chris Packham <judge.pack...@gmail.com> --- Hi, I noticed --recurse-submodules was missing from the bash completion. This adds it. I went for '--recurse-submodules' instead of '--recursive' as I seem to recall the former being agreed upon as the better (or least amb

git diff A...B is both overly forgiving and weird

apparently substituted in for the merge-base.) Chris commit 2b9288cc90175557766ef33e350e0514470b6ad4 Author: Chris Torek <chris.to...@gmail.com> Date: Tue Jul 5 05:15:23 2016 -0700 git diff: improve A...B merge-base handling When git diff is given a symmetric difference A...B, it

Re: [bug] assertion in 2.8.4 triggering on old-ish worktree

On Fri, Jun 17, 2016 at 7:48 AM, Stefan Beller <sbel...@google.com> wrote: > On Thu, Jun 16, 2016 at 10:59 AM, Junio C Hamano <gits...@pobox.com> wrote: >> Chris Packham <judge.pack...@gmail.com> writes: >> >>> On Thu, Jun 16, 2016 at 4:59 PM, Chris Pa

Re: [bug] assertion in 2.8.4 triggering on old-ish worktree

On Thu, Jun 16, 2016 at 4:59 PM, Chris Packham <judge.pack...@gmail.com> wrote: > Hi All, > > I have the git-sh-prompt configured in my .bashrc today I visited an > old worktree that I haven't really touched in a few years (sorry can't > remember the git version I was using b

[bug] assertion in 2.8.4 triggering on old-ish worktree

Hi All, I have the git-sh-prompt configured in my .bashrc today I visited an old worktree that I haven't really touched in a few years (sorry can't remember the git version I was using back then). I received the following output when changing to the directory git: pathspec.c:317:

DONATION OF $ 1.5 MILLION DOLLARS!!!

. Best of luck. Colin & Chris Weir -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: git push --quiet option does not seem to work

>> Once I included the whole email in my reply, but otherwise I deleted it >> all. > Both are bad practice. If you are considerate with the reader's time, this > consideration is typically reprocicated. So it is a good idea to save the > reader time by giving them the precise context they need.

Re: git push --quiet option does not seem to work

Once I included the whole email in my reply, but otherwise I deleted it all. Anyway, it is not a Powershell thing. I tested on another repo on GitHub and it worked as expected. So I guess indeed the problem lies with Microsoft's implementation. -- To unsubscribe from this list: send the line

Re: git push --quiet option does not seem to work

PS H:\test-ps\myrepo> "hi" >> whatever PS H:\test-ps\myrepo> git add . PS H:\test-ps\myrepo> git commit -m 'boo' [test1 3cde450] boo Committer: Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate.

Re: git push --quiet option does not seem to work

I did not see in your example any commit. But if you say so. I saw git init which would be a new repo.. don't know if it makes a difference. It's pushing to HTTPS. I can provide the real example tomorrow. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message

Re: git push --quiet option does not seem to work

By the way, I also notice by your prompt you seem to be testing this in Linux. I did indicate I'm using the Windows version. That might make a difference. On Sun, May 15, 2016 at 4:29 PM, Chris B <chris.blaszczyn...@gmail.com> wrote: > Try it by making some changes to files and commit

Re: git push --quiet option does not seem to work

t;p...@peff.net> wrote: > On Fri, May 13, 2016 at 05:21:30PM -0400, Chris B wrote: > >> Hi I am using 2.8.2.windows.1 and writing Powershell scripts doing >> some Git stuff. >> >> I have to use the --quiet option for git because it constantly outputs >> p

git push --quiet option does not seem to work

Hi I am using 2.8.2.windows.1 and writing Powershell scripts doing some Git stuff. I have to use the --quiet option for git because it constantly outputs progress to stderr. However, it seems that --quiet does not actually work in git push. The output still goes to stderr. When there are changes

Re: Triangular workflows and some anecdotes from the trenches

On Wed, Apr 6, 2016 at 10:24 AM, Junio C Hamano <gits...@pobox.com> wrote: > Chris Packham <judge.pack...@gmail.com> writes: > >> We ran into something at $dayjob the other day. The actual problem was >> a developer ended up amending a commit that had alre

Triangular workflows and some anecdotes from the trenches

wondering if something more official can be added to git commit --amend (and probably git rebase). Finally I was wondering if there is any way of detecting if remote.*.pushurl and remote.*.url point to the same repo, although I'm not sure when you'd do such verification. Thanks, Chris

Re: git difftool help

On Tue, Mar 29, 2016 at 3:07 AM, ratheesh kannoth wrote: > 'git diff 'is opening in meld. I could not create a patch using - git > diff > ./patch-01 > i did not make any change to pick meld, by default it is picking meld. > > > Which "git difftool" will help to create

Re: Problem with git-http-backend.exe as iis cgi

Hi Florian On Tue, Mar 29, 2016 at 7:01 PM, Florian Manschwetus wrote: > Hi, > I put together a first patch for the issue. > > Mit freundlichen Grüßen / With kind regards > Florian Manschwetus > > E-Mail: manschwe...@cs-software-gmbh.de > Tel.: +49-(0)611-8908534

[BUG] pre-applypatch can no longer add to staging area

voked with the changes applied but before they are committed so it should be OK to add additional changes to the staging area as part of the hook. Interestingly with the newer git version the change is not even staged. Thanks, Chris -- To unsubscribe from this list: send the line "unsubscribe

Re: Why are submodules not automatically handled by default or at least configurable to do so?

On Mon, Oct 26, 2015 at 12:10 PM, John Smith wrote: > I found that I use submodules much, much more often in my git projects than I > used externals > in Subversion and the reason is that git encourages/forces to organize large > projects into > smaller repositories, one

Re: [BUG?] applypatch-msg hook no-longer thinks stdin is a tty

On Sat, Oct 3, 2015 at 6:43 AM, Junio C Hamano <gits...@pobox.com> wrote: > Junio C Hamano <gits...@pobox.com> writes: > >> Chris Packham <judge.pack...@gmail.com> writes: >> >>> As of git 2.6 this has stopped working and stdin always fails the t

[BUG?] applypatch-msg hook no-longer thinks stdin is a tty

Hi, I have a applypatch-msg hook that implements some policy for acceptable commit messages and reject non-conformant patches. It also is able to prompt me to override it's rejection. The prompting only happens when stdin is a tty (as determined by pythons sys.stdin.isatty()) For example this

Re: storing cover letter of a patch series?

On Fri, Sep 11, 2015 at 4:28 AM, Jacob Keller wrote: > Hey, > > does anyone know of any tricks for storing a cover letter for a patch > series inside of git somehow? I'd guess the only obvious way currently > is to store it at the top of the series as an empty commit.. but

Re: Git book figure bug

On Wed, Sep 2, 2015 at 7:45 PM, Jesper Jørgensen wrote: > Hi, > > I am learning how git works, and is using the excellent book on the official > site. > I believe I have located a mistake in one of the images. > It is about Figure 3.17 on this page : >

Re: [PATCH] git-submodule: remove extraneous space from error message

\$sha1') must_die_on_failure=yes ;; -- 2.5.0 Looks good to me. Thanks Reviewed-by: Chris Packham judge.pack...@gmail.com -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord

Re: [PATCH 0/7] Flags and config to sign pushes by default

Bike shedding a little (I've never used the signed push functionality) On Fri, Aug 14, 2015 at 7:00 AM, Dave Borowitz dborow...@google.com wrote: The if-possible name and weird tri-state boolean is basically a straw man, and I am happy to change if someone has a clearer suggestion. what about

Error when cloning with weird local directory

that there is a problem worth solving here. I can provide an anonymized tarball of the directory structure in question if anyone is interested. But maybe this is useful for future mailing list searchers[1]. Thanks, Chris -- [1] - https://xkcd.com/979/ -- To unsubscribe from this list: send the line unsubscribe

Re: default configuration files on cygwin

On Tue, Jul 28, 2015 at 7:10 PM, Filippo Gatti filippo.ga...@centralesupelec.fr wrote: Hi, I'm currently running git on a cygwin platform. I would like to know how i can set up a sort of configuration file to launch automatically the ssh-agent and get connected to github (for istance)

Re: [PATCH] git-filter-branch.sh: clarify an error message

How does You did not provide a valid range of commits. At least one tip in your range must be a ref. sound? -- Chris http://christopherjones.us/ On Sun, Jul 5, 2015, at 10:41 AM, Johannes Schindelin wrote: Hi, On 2015-07-05 15:07, Jeff King wrote: On Sat, Jul 04, 2015 at 07:39:04PM

[PATCH] git-filter-branch.sh: clarify an error message

of commits to rewrite. This makes it give an error message that says You didn't provide a valid range of commits. Signed-off-by: Chris W Jones ch...@christopherjones.us --- git-filter-branch.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/git-filter-branch.sh b/git-filter

gitk: argument list too long

I've recently had an issue where running gitk --all has stopped working on a large repository of mine. Gitk's main window appears with all of the sections empty, and a modal tells me 'Error executing git log: couldn't execute git: argument list too long'. I'm on OS X, and am running git version

bug report : 2.3.5 ssh repo not found

to my distro's last installed version of git version 2.2.2 and now I can clone / pull / push to/from that repo without issue. Is this a bug? Best, Chris -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info

Re: git-archive ignores submodules

On Fri, Apr 17, 2015 at 7:59 AM, Pedro Rodrigues prodrigues1...@gmail.com wrote: snip Not completely off topic, but for consistency consider that: git-clone supports --recursive and --recurse-submodules, which do the same thing. git-pull and git-push only support --recurse-submodules. It

Re: rebase --root conflicts with --committer-date-is-author-date

Junio C Hamano gits...@pobox.com wrote: Chris, do you remember if there was a reason why it was a bad idea to teach the normal rebase codepath to handle --root? I think we would have needed to allow am to apply a creation patch and start a new history on an unborn branch in order to do so

Re: Feature Request: provide cmdline args to git hooks

I do not offhand know (I am on a bus with terrible connection so I won't bother checking the source now) if we send this ref has to point at that object even for STATUS_UPTODATE cases, to cause your remote to trigger the receive hook in the frist place, but if that is the case, then the code

Re: Feature Request: provide cmdline args to git hooks

Unfortunately in this case we don't have control over the hooks at the receiving end - we want to prevent tags from being pushed by all users to these repo's. On Wed, Apr 15, 2015 at 1:08 AM, Junio C Hamano gits...@pobox.com wrote: Chris O'Kelly ch...@mapcreative.com.au writes: A brief

Feature Request: provide cmdline args to git hooks

Hello, Just a brief note about a feature I would find incredibly useful, were it available. A brief background of my use case: I am wanting to write a pre-push hook to prevent tags being pushed to our production servers. The production servers in our case are --bare endpoints, and when we push a

Re: [bug (maybe)] Applying patch with '---'

On Wed, Apr 1, 2015 at 7:20 PM, Junio C Hamano gits...@pobox.com wrote: Chris Packham judge.pack...@gmail.com writes: So I was just sent a patch generated with 'git format-patch' that 'git am' fails to apply correctly. It applies but part of the commit message is lost. The problem

[bug (maybe)] Applying patch with '---'

of '---'. Regards, Chris -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Need help deciding between subtree and submodule

My $0.02 based on $dayjob (disclaimer I've never used subtree) On Wed, Mar 18, 2015 at 11:14 AM, Robert Dailey rcdailey.li...@gmail.com wrote: At my workplace, the team is using Atlassian Stash + git We have a Core library that is our common code between various projects. To avoid a single

Re: git submodule: update=!command

A little late to this thread On Wed, Mar 18, 2015 at 8:50 AM, Jeff King p...@peff.net wrote: On Tue, Mar 17, 2015 at 03:28:57PM -0400, Ryan Lortie wrote: The first is a question about git's basic policy with respect to things like this. I hope that it's safe to assume that running 'git'

Re: git submodule: update=!command

On Wed, Mar 18, 2015 at 10:05 AM, Junio C Hamano gits...@pobox.com wrote: Ryan Lortie de...@desrt.ca writes: On Tue, Mar 17, 2015, at 16:49, Junio C Hamano wrote: With more recent versions of Git, namely, the versions after 30a52c1d (Merge branch 'ms/submodule-update-config-doc' into maint,

Re: git submodule: update=!command

On Wed, Mar 18, 2015 at 8:43 PM, Chris Packham judge.pack...@gmail.com wrote: On Wed, Mar 18, 2015 at 10:05 AM, Junio C Hamano gits...@pobox.com wrote: Ryan Lortie de...@desrt.ca writes: On Tue, Mar 17, 2015, at 16:49, Junio C Hamano wrote: With more recent versions of Git, namely

git-describe considers WC dirty incorrectly when using --git-dir

It seems that git-describe always thinks that working copy is dirty if you are not in the WC root and you explicitly specify the .git directory location using --git-dir: # set up test repo folio:~ chris$ mkdir repo cd repo folio:repo chris$ mkdir text echo hi text/hi.txt folio:repo

Re: git-describe considers WC dirty incorrectly when using --git-dir

On Wed, Mar 4, 2015 at 11:54 AM, Junio C Hamano gits...@pobox.com wrote: Chris Pimlott ch...@pimlott.net writes: folio:text chris$ git --git-dir=../.git describe --always --dirty c0edd63-dirty I have a feeling that this is not limited to describe at all. With the --git-dir option, you

Re: Windows Bluescreen

issue with windows, but can't find it now. https://github.com/msysgit/git/issues Happy hunting :). Actually if it is a ssh problem it might be a generic MSYS issue. So there's another bug tracker to look through http://sourceforge.net/p/mingw/bugs/ On Wed, Feb 11, 2015 at 3:56 AM, Chris Packham

Re: Windows Bluescreen

Hi Erik, On Tue, Feb 10, 2015 at 9:12 AM, e...@aercon.net wrote: I find that preview 1.8 is bluescreening on about 1 of 3 ssh pushes. 1.9 preview 12-17-2014 doesn't even bluescreen, the windows gui locks until reset. Does this mean that pushing over git:// file:// and http:// are

Re: [PATCH 1/2] Fixes _is_git

+ if {[regexp ^gitdir: (.+)$ $line line link_target]} { 2015-02-03 3:44 UTC-05:00, Chris Packham judge.pack...@gmail.com: It might be simpler to use one of the 'string' commands e.g. string wordend gitdir: I also suspect the string functions would be faster than regexp

Re: [PATCH 1/2] Fixes _is_git

Hi Remi, Added Pat Thoyts the git-gui maintainer. (Disclaimer, it's been years since I did anything with Tcl). On Tue, Feb 3, 2015 at 6:24 AM, Remi Rampin remiram...@gmail.com wrote: Function _git_dir would previously fail to accept a gitdir: ... file as a valid Git repository. ---

  1   2   3   4   >