Re: Pls Support Conservancy: https://sfconservancy.org/supporter/

I just wanted to add that the Conservancy does really important, thankless work on a shoestring budget. I've known Bradley and Karen for years and I've seen how dedicated they are to keeping free software free. I'm a Conservancy supporter, and I hope you'll join up too! On Tue, 2015-12-22 at

Re: git objects

On Thu, Dec 24, 2015 at 2:17 PM, Thiago Farina wrote: > > When ever I make a commit (assume I'm changing a single file) and do a > 'git push origin master', git says 'Counting objects: 6, done.' > > Does git makes 6 objects everytime? What are those objects? 1 commit object;

Re: [PATCH v3 10/11] config: add core.untrackedCache

On Thu, Dec 24, 2015 at 11:13 AM, Duy Nguyen wrote: > On Thu, Dec 24, 2015 at 4:03 AM, Christian Couder > wrote: >> --force-untracked-cache:: >> - For safety, `--untracked-cache` performs tests on the working >> - directory to make sure

git objects

Hi, When ever I make a commit (assume I'm changing a single file) and do a 'git push origin master', git says 'Counting objects: 6, done.' Does git makes 6 objects everytime? What are those objects? -- Thiago Farina -- To unsubscribe from this list: send the line "unsubscribe git" in the body

Re: Building Git with HTTPS support: avoiding libcurl?

On Tue, Dec 22, 2015 at 1:39 PM, Paul Smith wrote: > I'm trying to build Git (2.6.4) on GNU/Linux, but without any > requirements (other than basic libc etc.) on the local system. This > works fine except for one thing: git-remote-https. > > In order to build this I need

Re: [PATCH 7/8] config: add core.untrackedCache

On Thu, Dec 24, 2015 at 2:56 AM, Junio C Hamano wrote: > Junio C Hamano writes: > >> Duy Nguyen writes: >> >>> In that case we can just check config once in read_index_from and >>> destroy UNTR extension. Or the middle ground, we check

Re: [PATCH v3 04/11] update-index: add untracked cache notifications

On Thu, Dec 24, 2015 at 11:01 AM, Duy Nguyen wrote: > On Thu, Dec 24, 2015 at 4:03 AM, Christian Couder > wrote: >> @@ -1135,10 +1135,16 @@ int cmd_update_index(int argc, const char **argv, >> const char *prefix) >> } >>

Re: "git stash pop" is doing an unwanted "git add" when there are conflicts.

Hello, Jeff. On Tue, Dec 22, 2015 at 04:30:33AM -0500, Jeff King wrote: > On Tue, Dec 22, 2015 at 09:17:38AM +0100, Dennis Kaarsemaker wrote: > > On ma, 2015-12-21 at 14:29 +, Alan Mackenzie wrote: > > > Hello, git project. > > > Last night, whilst clearing out a stale "stash stack", I did

Re: [PATCH v2 0/3] nd/clear-gitenv-upon-use-of-alias

On Thu, Dec 24, 2015 at 4:31 AM, Jeff King wrote: > 2. I doubt anybody is actually seeing this in practice anymore. But > maybe I am misunderstanding something in Duy's series that changes > this. There are two parts in your patch, one (that you two seemed to focus on)

Re: [PATCH v2 10/11] ref-filter: introduce contents_atom_parser()

On Thu, Dec 17, 2015 at 3:09 PM, Eric Sunshine wrote: > On Wed, Dec 16, 2015 at 10:30 AM, Karthik Nayak wrote: >> Introduce contents_atom_parser() which will parse the '%(contents)' >> atom and store information into the 'used_atom' structure based

Re: [PATCH v3 10/11] config: add core.untrackedCache

On Thu, Dec 24, 2015 at 4:03 AM, Christian Couder wrote: > --force-untracked-cache:: > - For safety, `--untracked-cache` performs tests on the working > - directory to make sure untracked cache can be used. These > - tests can take a few seconds.

Re: [PATCH 7/8] config: add core.untrackedCache

On Thu, Dec 24, 2015 at 8:56 AM, Junio C Hamano wrote: > Junio C Hamano writes: > >> Duy Nguyen writes: >> >>> In that case we can just check config once in read_index_from and >>> destroy UNTR extension. Or the middle ground, we check

Re: [PATCH v3 04/11] update-index: add untracked cache notifications

On Thu, Dec 24, 2015 at 4:03 AM, Christian Couder wrote: > Attempting to flip the untracked-cache feature on for a random index > file with > > cd /random/unrelated/place > git --git-dir=/somewhere/else/.git update-index --untracked-cache > > would not work as

Re: [PATCH v1 2/2] git-p4: suppress non test relevant output

On 22/12/15 08:47, Lars Schneider wrote: On 21 Dec 2015, at 21:38, Junio C Hamano wrote: If so, why not do it there instead? You seem to run only "kill" to send some signal to a process using this helper function, and it would be silent on its standard output stream