Duy Nguyen pclouds at gmail.com writes:
On Tue, Feb 4, 2014 at 12:13 PM, chris jugg at hotmail.com wrote:
However, I question why I should even care about this message? I'm going to
assume that simply it is a lengthy synchronous operation that someone felt
deserved some verbosity to why
chris j...@hotmail.com writes:
Duy Nguyen pclouds at gmail.com writes:
On Tue, Feb 4, 2014 at 9:20 AM, chris jugg at hotmail.com wrote:
$ git push origin next
Counting objects: 56, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects:
David Kastrup dak at gnu.org writes:
chris jugg at hotmail.com writes:
Duy Nguyen pclouds at gmail.com writes:
On Tue, Feb 4, 2014 at 9:20 AM, chris jugg at hotmail.com wrote:
$ git push origin next
Counting objects: 56, done.
Delta compression using up to 4 threads.
Compressing
chris j...@hotmail.com writes:
David Kastrup dak at gnu.org writes:
chris jugg at hotmail.com writes:
Duy Nguyen pclouds at gmail.com writes:
On Tue, Feb 4, 2014 at 9:20 AM, chris jugg at hotmail.com wrote:
$ git push origin next
Counting objects: 56, done.
Delta compression using
David Kastrup dak at gnu.org writes:
chris jugg at hotmail.com writes:
That said I would naively assume that a server side house keeping
operation that does not get invoked with every client request be a
nice candidate for asynchronous handling without any need to tell the
client about
chris j...@hotmail.com writes:
Ok, given your full response, I understand how this is being
conceptualized now, thanks. However, if you look at it purely from a
user's perspective who is manually invoking these commands for the
command's primary purpose, the current behavior is annoying.
Hi,
I have garbage collection disabled globally with gc.auto = 0. Today while
pushing a branch remotely, I saw a message Auto packing the repository for
optimum performance. which I've never noticed before. Searching for that
phrase shows me that common knowledge is that 'gc.auto = 0' should
On Tue, Feb 4, 2014 at 9:20 AM, chris j...@hotmail.com wrote:
$ git push origin next
Counting objects: 56, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 895 bytes | 0 bytes/s, done.
Total 9 (delta 8), reused 0 (delta 0)
Duy Nguyen pclouds at gmail.com writes:
On Tue, Feb 4, 2014 at 9:20 AM, chris jugg at hotmail.com wrote:
$ git push origin next
Counting objects: 56, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (9/9), 895 bytes | 0 bytes/s,
On Tue, Feb 4, 2014 at 12:13 PM, chris j...@hotmail.com wrote:
However, I question why I should even care about this message? I'm going to
assume that simply it is a lengthy synchronous operation that someone felt
deserved some verbosity to why the client push action is taking longer than
it
10 matches
Mail list logo
