The pkt-line formatted lines contained the wrong pkt-len.
Signed-off-by: Mike Hommey
---
Documentation/technical/pack-protocol.txt | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/technical/pack-protocol.txt
b/Documentation/technical/pack-protocol.txt
in
From: Johannes Schindelin
This one is tricky.
When `core.fsmonitor` is set, a `refresh_index()` will not perform a
full scan of files that might be modified, but will query the fsmonitor
and refresh only the ones that have been actually touched.
Due to implementation details, the fsmonitor is q
It was reported by Ævar Arnfjörð Bjarmason
[https://public-inbox.org/git/nycvar.qro.7.76.6.1903142058130...@tvgsbejvaqbjf.bet/T/#mb8718fe52e4721dacd3b143a09187ff9090ef4e3]
that there were problems with the fsmonitor feature in conjunction with the
newly built-in git stash/git rebase.
The culprit
From: Johannes Schindelin
With this change, the `index_state` struct becomes the new home for the
flag that says whether the fsmonitor hook has been run, i.e. it is now
per-index.
It also gets re-set when the index is discarded, fixing the bug where
fsmonitor-enabled Git would miss updates under
Am 16.03.19 um 10:49 schrieb Johannes Schindelin via GitGitGadget:
> diff --git a/t/t7519-status-fsmonitor.sh b/t/t7519-status-fsmonitor.sh
> index 3e0a61db23..918bc323ab 100755
> --- a/t/t7519-status-fsmonitor.sh
> +++ b/t/t7519-status-fsmonitor.sh
> @@ -346,4 +346,14 @@ test_expect_success UNTRAC
Signed-off-by: Alexander Blesius
---
Documentation/git-worktree.txt | 4 ++--
Documentation/gitattributes.txt | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-worktree.txt b/Documentation/git-worktree.txt
index cb86318f3e..fa5ec7a5dc 100644
--- a/Documen
From: Torsten Bögershausen
Some compilers don't allow NULL to be passed for a va_list.
Use va_list instead.
Signed-off-by: Torsten Bögershausen
---
trace2.c| 15 +++
trace2.h| 4 ++--
trace2/tr2_tgt_event.c | 2 +-
trace2/tr2_tgt_normal.c | 2 +-
On Sat, 16 Mar 2019, Duy Nguyen wrote:
> On Fri, Mar 15, 2019 at 9:31 PM Robert P. J. Day
> wrote:
> > also, i think "man git-clone" could really use a set of examples for
> > shallow cloning. i'd offer to write it but i'm still figuring it out.
>
> Cool. I'll give you a quick introduction to
more nitpicking, but i'm working my way through the intricacies of
attributes and putting together some (allegedly) simple examples for a
class i'm giving on monday, and i noted a couple possible shortcomings
in "man gitattributes".
as a working example, i looked at the top-level .gitattribu
On Sat, Mar 16 2019, Robert P. J. Day wrote:
> more nitpicking, but i'm working my way through the intricacies of
> attributes and putting together some (allegedly) simple examples for a
> class i'm giving on monday, and i noted a couple possible shortcomings
> in "man gitattributes".
>
> as
On Sat, 16 Mar 2019, Ævar Arnfjörð Bjarmason wrote:
>
> On Sat, Mar 16 2019, Robert P. J. Day wrote:
>
> > more nitpicking, but i'm working my way through the intricacies of
> > attributes and putting together some (allegedly) simple examples for a
> > class i'm giving on monday, and i noted a c
On Thu, Feb 21, 2019 at 9:24 AM Jeff King wrote:
>
> On Wed, Feb 20, 2019 at 11:59:04PM -0500, Jeff King wrote:
>
> > On Wed, Feb 20, 2019 at 02:03:40PM +0100, Ævar Arnfjörð Bjarmason wrote:
> >
> > > > I wanted to point a colleague of mine to one of the talks.
> > > > Unfortunately I could not fi
Hello, with due respect, I am Lawson Nkatara Esq. I want to know if
you actually got the previous email I sent to you.
Kyle Meyer writes:
[...]
> diff --git a/git-submodule.sh b/git-submodule.sh
> index 514ede2596..6c74656027 100755
> --- a/git-submodule.sh
> +++ b/git-submodule.sh
> @@ -234,10 +234,18 @@ cmd_add()
> if test -z "$force" &&
> ! git add --dry-run --ignore-missing --no-warn-embe
[please keep everyone in Cc, especially the mailing list if you are
responding to review comments. I added the Cc's back]
On 03/16, Kapil Jain wrote:
> On Sat, Mar 16, 2019 at 4:35 AM Thomas Gummerer wrote:
> >
> > For testing you could have a look how other userdiff drivers are
> > tested in t4
Since commit ef0cc1df90f6b ("send-email: also pick up cc addresses from
-by trailers") in git version 2.20, git send-email adds to cc list
addresses from all *-by lines. As a side effect a line with
'-Signed-off-by' is now also added to cc. This makes send-email pick
lines from patches that remove
On Sat, 2019-03-16 at 21:26 +0200, Baruch Siach wrote:
> Since commit ef0cc1df90f6b ("send-email: also pick up cc addresses from
> -by trailers") in git version 2.20, git send-email adds to cc list
> addresses from all *-by lines. As a side effect a line with
> '-Signed-off-by' is now also added to
Hi Joe,
On Sat, Mar 16 2019, Joe Perches wrote:
> On Sat, 2019-03-16 at 21:26 +0200, Baruch Siach wrote:
>> Since commit ef0cc1df90f6b ("send-email: also pick up cc addresses from
>> -by trailers") in git version 2.20, git send-email adds to cc list
>> addresses from all *-by lines. As a side effe
On Sat, 2019-03-16 at 21:49 +0200, Baruch Siach wrote:
> Hi Joe,
>
> On Sat, Mar 16 2019, Joe Perches wrote:
> > On Sat, 2019-03-16 at 21:26 +0200, Baruch Siach wrote:
> > > Since commit ef0cc1df90f6b ("send-email: also pick up cc addresses from
> > > -by trailers") in git version 2.20, git send-e
Just pass it on down to builtin/repack.
Signed-off-by: Nathaniel Filardo
---
Documentation/git-gc.txt | 5 +
builtin/gc.c | 5 +
2 files changed, 10 insertions(+)
diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt
index a7c1b0f60e..7115564f7d 100644
--- a/Docum
The sparse connectivity algorithm saves a whole lot of time when there
are UNINTERESTING trees around.
---
Documentation/git-repack.txt | 4
builtin/repack.c | 5 +
t/t5322-pack-objects-sparse.sh | 6 ++
3 files changed, 15 insertions(+)
diff --git a/Documentation/git
If the user is careful to mark .pack files as kept only when they refer
to (other) kept packs, then we can rely on this when walking the object
graph in subsequent repack operations and reduce the time and memory
spent building the object graph.
Towards that end, then, teach git repack to enumerat
This patch series improves handling of very large repositories, as generated
by, for example, bup (https://github.com/bup/bup). Prolonged operation
thereof creates quite a lot of small pack files; repacking improves
filesystem performance of the objects/pack directory, but is quite
expensive, in t
Specifically: number of kept packs, size of kept packs (and indexes),
and number of objects in kept packs.
Add documentation of resulting fields. While here, correct the omission
from ae72f68541 ("count-objects -v: show number of packs as well.",
2006-12-27) of the "packs" field.
Signed-off-by:
Add another bit flag to the struct rev_info.
The only caller that uses this after this patch is builtin/pack-objects.
Without this, sparsity seems to do little good therein, as
prepare_revision_walk will densely propagate UNINTERESTING flags from
trees to tree contents, before mark_edges_uninteres
Hi Joe,
On Sat, Mar 16 2019, Joe Perches wrote:
> On Sat, 2019-03-16 at 21:49 +0200, Baruch Siach wrote:
>> On Sat, Mar 16 2019, Joe Perches wrote:
>> > On Sat, 2019-03-16 at 21:26 +0200, Baruch Siach wrote:
>> > > Since commit ef0cc1df90f6b ("send-email: also pick up cc addresses from
>> > > -by
On Sat, 2019-03-16 at 22:14 +0200, Baruch Siach wrote:
> Hi Joe,
Hello Baruch.
> On Sat, Mar 16 2019, Joe Perches wrote:
> > So buildroot uses '+Signed-off-by:' and '-Signed-off-by:' lines
> > for some internal purpose?
> >
> > Why?
> >
> > https://buildroot.org/downloads/manual/manual.html
> >
I'm trying to transform a repository from another VCS into a Git
repository using "git fast-import". It appears to work, but the
resulting Git repository is huge relative to the original - 18 times
larger. Most of the space seems to be taken up by a single large
packfile. That packfile is about 9
On Sat, Mar 16, 2019 at 1:31 PM Richard Hipp wrote:
>
> Maybe I'm doing something wrong with the fast-import stream that is
> defeating Git's attempts at delta compression
fast-import doesn't do fancy delta compression becayse that would
defeat the "fast" part of fast-import.
Just do a git r
Sent from my iPhone this is my new phone and number
Am 16.03.19 um 13:22 schrieb Robert P. J. Day:
> as a working example, i looked at the top-level .gitattributes file
> in the git source code itself, which opens with:
>
> * whitespace=!indent,trail,space
> *.[ch] whitespace=indent,trail,space diff=cpp
> *.sh whitespace=indent,trail,space
On Sat, 16 Mar 2019, Johannes Sixt wrote:
> Am 16.03.19 um 13:22 schrieb Robert P. J. Day:
> > as a working example, i looked at the top-level .gitattributes file
> > in the git source code itself, which opens with:
> >
> > * whitespace=!indent,trail,space
> > *.[ch] whitespace=indent,trail,
On Sat, Mar 16, 2019 at 02:04:33PM -0700, Linus Torvalds wrote:
> On Sat, Mar 16, 2019 at 1:31 PM Richard Hipp wrote:
> >
> > Maybe I'm doing something wrong with the fast-import stream that is
> > defeating Git's attempts at delta compression
>
> fast-import doesn't do fancy delta compressio
Sent from my iPhone this is my new phone and number
Amitie vrai source de vie, le partager avec toi serait une joie
sincerement
---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel
antivirus Avast.
https://www.avast.com/antivirus
On 3/16/19, Linus Torvalds wrote:
>
>git repack -adf
>
Thanks for the tip!
--
D. Richard Hipp
d...@sqlite.org
One-way merge is supposed to take stat info from the index and
everything else from the given tree. This implies stage 0 because trees
can't have non-zero stages. The add_entry(.., old, ...) call however
will keep stage index from the index.
This is normally not a problem if the entry from the ind
37 matches
Mail list logo
