From: Thomas Rast
These are essentially lifted from https://github.com/trast/tbdiff, with
light touch-ups to account for the command now being named `git
range-diff`.
Apart from renaming `tbdiff` to `range-diff`, only one test case needed
to be adjusted: 11 - 'changed message'.
The underlying
From: Thomas Rast
These are essentially lifted from https://github.com/trast/tbdiff, with
light touch-ups to account for the command now being named `git
range-diff`.
Apart from renaming `tbdiff` to `range-diff`, only one test case needed
to be adjusted: 11 - 'changed message'.
The underlying
From: Thomas Rast
These are essentially lifted from https://github.com/trast/tbdiff, with
light touch-ups to account for the command now being names `git
range-diff`.
Apart from renaming `tbdiff` to `range-diff`, only one test case needed
to be adjusted: 11 - 'changed message'.
The underlying
From: Thomas Rast
These are essentially lifted from https://github.com/trast/tbdiff, with
light touch-ups to account for the command now being an option of `git
branch`.
Apart from renaming `tbdiff` to `range-diff`, only one test case needed
to be adjusted: 11 - 'changed message
operations as DJB.
I don't think there's a point in having such a function, since it would
mean a lot of code for no throughput gain. Let's just remove
XDL_FAST_HASH and the original hashing scheme in favor of a better hash
function.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list
Eric Sunshine sunsh...@sunshineco.com writes:
On Sat, Feb 22, 2014 at 4:17 AM, Thomas Rast t...@thomasrast.ch wrote:
-static void lazy_init_name_hash(struct index_state *istate)
+void init_name_hash(struct index_state *istate, int force_dir_hash)
{
int nr;
if (istate
that we no longer need
(in 8/8); previously, the insert-only name-hash kept them alive.
- Adaptations to match Duy's changes to cache_tree handling (in 8/8).
Please review the cache_tree handling extra carefully, as I'm not
100% convinced the dance there is all that is needed.
Thomas Rast
From: Thomas Rast tr...@inf.ethz.ch
650467c (merge-recursive: Consolidate different update_stages
functions, 2011-08-11) changed the former argument 'clear' to always
be true. Remove the useless conditional.
Signed-off-by: Thomas Rast tr...@inf.ethz.ch
Signed-off-by: Junio C Hamano gits
commit will simplify this to a single setting again.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
builtin/diff.c | 3 +--
combine-diff.c | 13 ++---
diff-lib.c | 6 ++
diff.h | 6 +++---
log-tree.c | 2 +-
submodule.c| 5 -
6 files changed, 17
From: Thomas Rast tr...@inf.ethz.ch
o-call_depth has a double function: a nonzero call_depth means we
want to construct virtual merge bases, but it also means we want to
avoid touching the worktree. Introduce a new flag o-no_worktree to
trigger only the latter.
Signed-off-by: Thomas Rast tr
variants without yet more
special casing. It should also be slightly easier to read because one
does not have to ensure that the flag bits are set in an expected
combination.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
builtin/diff-files.c| 5 +++--
builtin/diff-tree.c | 2 +-
builtin
The directory hash (for fast checks if the index already has a
directory) was only used in ignore_case mode and so depended on that
flag.
Make it generally available on request.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
cache.h | 2 ++
name-hash.c | 13 -
2 files
get the _conflicts_ with --index-only,
but not (conveniently) the conflict-hunk formatted files that would
normally be written to the worktree.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
Documentation/merge-strategies.txt | 5 +
merge-recursive.c | 4
merge
From: Thomas Rast tr...@inf.ethz.ch
Using the new no_worktree flag from the previous commit, we can teach
merge-recursive to leave the worktree untouched. Expose this with a
new strategy option so that scripts can use it.
Signed-off-by: Junio C Hamano gits...@pobox.com
---
Documentation/merge
; and the
output is usually much shorter than with -c.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
Documentation/rev-list-options.txt | 7 +
log-tree.c | 297 +
merge-recursive.c | 3 +-
merge-recursive.h
Fabian Ruch baf...@gmail.com writes:
Hi Thomas,
Thomas Rast writes:
Fabian Ruch baf...@gmail.com writes:
@@ -923,6 +923,8 @@ EOF
;;
esac
+mkdir -p $state_dir || die Could not create temporary $state_dir
+
git var GIT_COMMITTER_IDENT /dev/null ||
die You need to set your
Fabian Ruch baf...@gmail.com writes:
Hi Thomas,
Thomas Rast writes:
Fabian Ruch baf...@gmail.com writes:
Subject: Re: [PATCH v2 08/23] rebase -i: reword executes pre-commit
hook on interim commit
I think the change makes sense, but can you reword the subjects that it
describes the state
expect expected
test_cmp expected actual
'
Getting rid of these magic removals is a very nice change, thank you.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
?
--
Thomas Rast
t...@thomasrast.ch
--
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
not require quoting through an eval?
Please add tests to this patch.
--
Thomas Rast
t...@thomasrast.ch
--
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
of do_replay?
--
Thomas Rast
t...@thomasrast.ch
--
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
could spell it 'reword' (with the quotes), which also disambiguates
the command from the verb.
--
Thomas Rast
t...@thomasrast.ch
--
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
...$orig_head
+ fi
shortrevisions=$shorthead
Nit: I think this would be clearer if you phrased it using an 'elif',
instead of nesting (but keep the comment!).
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord
, st, reason) ||
+ st.st_mtime expire)
causes the second arm to be evaluated when st.st_mtime is not
initialized yet. Can you look into this?
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord
as my shell and as /bin/sh, but I do have zsh installed.
Can you look into it?
--
Thomas Rast
t...@thomasrast.ch
--
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
Ralf Thielow ralf.thie...@gmail.com writes:
Translate 45 new messages came from git.pot update in 5e078fc
(l10n: git.pot: v2.0.0 round 1 (45 new, 28 removed)).
Thanks for sending this with extra context, it really helps reviewing!
With the small changes below,
Acked-by: Thomas Rast t
+
The microproject idea said
Rewrite diff-no-index.c:read_directory() to use
is_dot_or_dotdot(). Try to find other sites that can use that
function.
Are there any others?
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body
);
- free(args);
+ status = run_command_v_opt(argv.argv, RUN_GIT_CMD);
+ argv_array_clear(argv);
return status;
}
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
Michael Andreen h...@ruin.nu writes:
The --minimal flag is still there, but didn't want to break scripts
depending on it.
If I specify --no-minimal, does that turn it off again?
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body
,
+ (argc - i) * sizeof(char *));
This isn't right -- you are computing the size of things to be moved
based on a type of char*, but 'modes' is an enum.
(Valgrind spotted this.)
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body
Eric Sunshine sunsh...@sunshineco.com writes:
On Sat, Feb 22, 2014 at 4:17 AM, Thomas Rast t...@thomasrast.ch wrote:
Using the new no_worktree flag from the previous commit, we can teach
merge-recursive to leave the worktree untouched. Expose this with a
new strategy option so that scripts
Thomas Rast t...@thomasrast.ch writes:
Junio C Hamano gits...@pobox.com writes:
Thomas Rast t...@thomasrast.ch writes:
@@ -2845,8 +2845,9 @@ static struct diff_tempfile *prepare_temp_file(const
char *name,
remove_tempfile_installed = 1;
}
- if (!one-sha1_valid
. I'm
not completely happy yet -- see the NEEDSWORK comments -- but at
least it gives consistent input to the diffing stage.
This required access to the dir hash, so there's a new patch 7 that
makes this possible.
Patches 1-6 (used to be 1-3 and 6-8) are unchanged.
Thomas Rast (8):
merge
The directory hash (for fast checks if the index already has a
directory) was only used in ignore_case mode and so depended on that
flag.
Make it generally available on request.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
cache.h | 2 ++
name-hash.c | 19 ---
2 files
variants without yet more
special casing. It should also be slightly easier to read because one
does not have to ensure that the flag bits are set in an expected
combination.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
builtin/diff-files.c| 5 +++--
builtin/diff-tree.c | 2 +-
builtin
From: Thomas Rast tr...@inf.ethz.ch
650467c (merge-recursive: Consolidate different update_stages
functions, 2011-08-11) changed the former argument 'clear' to always
be true. Remove the useless conditional.
Signed-off-by: Thomas Rast tr...@inf.ethz.ch
Signed-off-by: Junio C Hamano gits
From: Thomas Rast tr...@inf.ethz.ch
o-call_depth has a double function: a nonzero call_depth means we
want to construct virtual merge bases, but it also means we want to
avoid touching the worktree. Introduce a new flag o-no_worktree to
trigger only the latter.
Signed-off-by: Thomas Rast tr
get the _conflicts_ with --index-only,
but not (conveniently) the conflict-hunk formatted files that would
normally be written to the worktree.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
Documentation/merge-strategies.txt | 5 +
merge-recursive.c | 4
merge
From: Thomas Rast tr...@inf.ethz.ch
Using the new no_worktree flag from the previous commit, we can teach
merge-recursive to leave the worktree untouched. Expose this with a
new strategy option so that scripts can use it.
Signed-off-by: Junio C Hamano gits...@pobox.com
---
Documentation/merge
Junio C Hamano gits...@pobox.com writes:
Thomas Rast t...@thomasrast.ch writes:
@@ -2845,8 +2845,9 @@ static struct diff_tempfile *prepare_temp_file(const
char *name,
remove_tempfile_installed = 1;
}
-if (!one-sha1_valid ||
-reuse_worktree_file(name, one
objects will be loosened. Gotta go
soon, didn't really test it, but I bet it'll work.
This looks correct to me.
This comes from abe601bb, right? The change looks correct to me, too.
Ow, sorry about that. Thanks for the fix!
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from
a computer can do beyond
(author, authordate), anyway. Perhaps someone with a clue in UIs --
that's definitely not me -- could make a website where users can
complete or correct the autogenerated mappings to go further.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line
, that will not show up in a --cc diff.
--
Thomas Rast
t...@thomasrast.ch
--
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
that?
This seems to come up every year or so:
http://thread.gmane.org/gmane.comp.version-control.git/110369/focus=110383
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
David Kastrup d...@gnu.org writes:
Thomas Rast t...@thomasrast.ch writes:
David Kastrup d...@gnu.org writes:
When comparing two branches, decorating the flat diff with the
respectively responsible commits seems like it would be nice to do/have
(the blame on the identical parts, in contrast
Duy Nguyen pclo...@gmail.com writes:
On Sun, Feb 9, 2014 at 2:03 AM, Thomas Rast t...@thomasrast.ch wrote:
Easy:
* Add -p 'e' when it fails to apply should offer an obvious way of
starting from the original hunk (not the broken one) or both
If it's too easy, you can add a command
had
bitrotted without anyone noticing. I haven't heard of any heavy users.
I originally wrote them to do some basic test coverage analysis, but
that's about it.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord
$sha1, but the new-file is a directory in
the worktree.
Fix it by never reusing a worktree file in the submodule case.
Reported-by: Grégory Pakosz gregory.pak...@gmail.com
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
diff.c | 5 +++--
t/t4020-diff-external.sh | 30
David Kastrup d...@gnu.org writes:
Thomas Rast t...@thomasrast.ch writes:
David Kastrup d...@gnu.org writes:
Looking in the Makefile, I just find support for coverage reports using
gcov. Whatever is there with profile in it seems to be for
profile-based compilation rather than using gprof
: C
Difficulty: hard
Possible mentors: Thomas Rast and fill in libgit2 expert
--- 8 ---
That absolutely requires a co-mentor from the libgit2 side to do,
however. Perhaps you could talk someone into it? ;-)
Motivation: I believe that migrating to libgit2 is the better approach,
medium term, than
Junio C Hamano gits...@pobox.com writes:
Thomas Rast t...@thomasrast.ch writes:
Downside: not listing code merged as a goal may not make the project
as shiny, neither for Git nor for the student.
I'd actually view that as an upside. This sounds like a good first
step for a feasibility
not be a piece of
advice that is practically very useful, though ;-)
That happens to me a lot, too. Perhaps it would be a clearer signal if
you had an alias (or just something like gitster+patch) that we can send
it to if we mean please include instead of what do you think of this?
--
Thomas
Typänderung:
#: wt-status.c:287
-#, fuzzy
msgid unknown
-msgstr unbekannt:%s
+msgstr unbekannt:
Do we still need the trailing colon?
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
.
Sorry for being so procrastinative :-(
I suggest we make it a rule that old projects cannot be proposed from
year to year.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
--
Thomas Rast
t...@thomasrast.ch
--
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
David Kastrup d...@gnu.org writes:
Thomas Rast t...@thomasrast.ch writes:
I don't really like 'gesondert eingehängt', how about 'transplantiert'
instead?
I suggest using the actual translation here as it is perfectly fitting
for both literal and figurative meaning: aufgepfropft.
I didn't
when
within 'git bisect run' -- probably there's something funky going on in
the environment, quite possibly in my own configs.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo
Kirill Smelkov k...@mns.spb.ru writes:
Since diff_tree_sha1() can now accept empty trees via NULL sha1, we
could just call it without manually reading trees into tree_desc and
duplicating code.
Cc: Thomas Rast t...@thomasrast.ch
Signed-off-by: Kirill Smelkov k...@mns.spb.ru
---
line
Hi,
This may look intimidating, but it's actually 3.5 separate things:
merge-recursive: remove dead conditional in update_stages()
merge-recursive: internal flag to avoid touching the worktree
merge-recursive: -Xindex-only to leave worktree unchanged
These are unchanged from
pp_commit_list() will be reused later.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
Necessary only for the next patch, which may be of dubious value.
commit.h | 1 +
pretty.c | 40 ++--
2 files changed, 27 insertions(+), 14 deletions(-)
diff --git
From: Thomas Rast tr...@inf.ethz.ch
650467c (merge-recursive: Consolidate different update_stages
functions, 2011-08-11) changed the former argument 'clear' to always
be true. Remove the useless conditional.
Signed-off-by: Thomas Rast tr...@inf.ethz.ch
Signed-off-by: Junio C Hamano gits
variants without yet more
special casing. It should also be slightly easier to read because one
does not have to ensure that the flag bits are set in an expected
combination.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
builtin/diff-files.c| 5 +++--
builtin/diff-tree.c | 2 +-
builtin
flags. This commit does not have
to: the commit graph will be loaded anyway, and the room for flags is
already there. As a big plus, this approach also works in a streaming
fashion, showing the first few commits very quickly.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
As indicated
commit will simplify this to a single setting again.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
builtin/diff.c | 3 +--
combine-diff.c | 13 ++---
diff-lib.c | 6 ++
diff.h | 6 +++---
log-tree.c | 2 +-
submodule.c| 5 -
6 files changed, 17
get the _conflicts_ with --index-only,
but not (conveniently) the conflict-hunk formatted files that would
normally be written to the worktree.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
Documentation/merge-strategies.txt | 5 +
merge-recursive.c | 4
merge
From: Thomas Rast tr...@inf.ethz.ch
o-call_depth has a double function: a nonzero call_depth means we
want to construct virtual merge bases, but it also means we want to
avoid touching the worktree. Introduce a new flag o-no_worktree to
trigger only the latter.
Signed-off-by: Thomas Rast tr
From: Thomas Rast tr...@inf.ethz.ch
Using the new no_worktree flag from the previous commit, we can teach
merge-recursive to leave the worktree untouched. Expose this with a
new strategy option so that scripts can use it.
Signed-off-by: Junio C Hamano gits...@pobox.com
---
Documentation/merge
; and the
output is usually much shorter than with -c.
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
Documentation/rev-list-options.txt | 7 ++
log-tree.c | 60 +++
merge-recursive.c | 3 +-
merge-recursive.h | 1
strikes a good balance in the complexity of the
protocol and the daemon's state.
--
Thomas Rast
t...@thomasrast.ch
--
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
tried
what happens if you point it at a bare though. It *should* fail because
it tries to cd $repo/.git, but if that was itself bare...
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
;
+ autorun_watcher = 1;
+ } else
+ git_config(watcher_config, NULL);
if (autorun_watcher == -1)
autorun_watcher = 0;
}
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line
, and behind the scenes issue all watches up to
the root even if we don't need them for anything other than directory
renames.
Ok, that's probably a confused sum of rambles. Let me know if you can
make any sense of it.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line
, newfd, data, sz) 0;
free(data);
--
Thomas Rast
t...@thomasrast.ch
--
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
.
--
Thomas Rast
t...@thomasrast.ch
--
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
The @{-N} syntax always referred to the N-th last thing checked out,
which can be either a branch or a commit (for detached HEAD cases).
However, the documentation only mentioned branches.
Edit in a /commit in the appropriate places.
Reported-by: Kevin i...@ikke.info
Signed-off-by: Thomas Rast t
triggering the bug with unpatched git-stash.
--
Thomas Rast
t...@thomasrast.ch
--
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
Ralf Thielow ralf.thie...@gmail.com writes:
The word 'prefix' is currently translated as 'Prefix'
which is not a German word. It should be translated as
'Präfix'.
Indeed :-)
Thanks!
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git
actual
+ test_cmp expect actual
+'
--
Thomas Rast
t...@thomasrast.ch
--
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
variables are unreferenced and then destroyed? I can't find any such
guarantee.
In the absence of such, wouldn't we have to keep $upa in an outer,
separate scope to ensure that $fbat is destroyed first?
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git
think it's a terrible choice because it suggests a
transaction between multiple people, which to me sounds like it should
mean push.)
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
if people find the above workarond a sensible thing to do in
git, I can submit a properly formed patch here too.
If you go this way, please add a comment that explains why we need the
local variable.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe
to actually make
sha1write's return code mean anything. But I just don't foresee that
happening.
Meh. It hasn't returned a useful value since its introduction in 2005.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message
, name_hash, 0, 0, index_pos, pack,
offset);
display_progress(progress_state, to_pack.nr_objects);
return 1;
}
Much nicer. Thanks for going the extra mile!
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body
Karsten Blees karsten.bl...@gmail.com writes:
Am 07.12.2013 23:23, schrieb Thomas Rast:
Karsten Blees karsten.bl...@gmail.com writes:
Extending 'struct hashmap_entry' with an int-sized member shouldn't waste
memory on 64-bit systems. This is already documented in api-hashmap.txt,
but needs
= found_offset;
@@ -859,10 +932,21 @@ static int add_object_entry(const unsigned char *sha1,
enum object_type type,
display_progress(progress_state, to_pack.nr_objects);
+ return 1;
+}
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git
of the support code is from
[10/21] ;-)
Reviewed-by: Thomas Rast t...@thomasrast.ch
--
Thomas Rast
t...@thomasrast.ch
--
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
(and otherwise rely on
rename() to barf).
Signed-off-by: Jeff King p...@peff.net
Reviewed-by: Thomas Rast t...@thomasrast.ch
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
want them on all the time.
Signed-off-by: Vicent Marti tan...@gmail.com
Signed-off-by: Jeff King p...@peff.net
Reviewed-by: Thomas Rast t...@thomasrast.ch
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord
.bitmap
files, the current code reports all such files as garbage
(case 1), even if their pack exists. Instead, they should be
treated as case 2.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
Signed-off-by: Jeff King p...@peff.net
Reviewed-by: Thomas Rast t...@thomasrast.ch
that using bitmaps does not break anything.
Signed-off-by: Jeff King p...@peff.net
Reviewed-by: Thomas Rast t...@thomasrast.ch
One nit:
+test_expect_success JGIT 'jgit can read our bitmaps' '
+ git clone . compat-us.git
+ (
+ cd compat-us.git
The name suggests a bare repo
test reproducible over time (not over
changing GIT_PERF_LARGE_REPO, of course).
--
Thomas Rast
t...@thomasrast.ch
--
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
Marti tan...@gmail.com
Signed-off-by: Jeff King p...@peff.net
Reviewed-by: Thomas Rast t...@thomasrast.ch
--
Thomas Rast
t...@thomasrast.ch
--
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
((__packed__)) with some compiler
detection in git-compat-util.h though.
--
Thomas Rast
t...@thomasrast.ch
--
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
and see which open window the address belongs
to. I need to think about the implications of doing that in a signal
handler, though.
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo
half of the series that led
up to ce2c58cd?
http://thread.gmane.org/gmane.comp.version-control.git/227151/focus=237937
--
Thomas Rast
t...@thomasrast.ch
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
further, but AFAICT it's just a rather obvious case
of duplication of effort.
--
Thomas Rast
t...@thomasrast.ch
--
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
Ramkumar Ramachandra artag...@gmail.com writes:
Thomas Rast wrote:
When --smtp-encryption=ssl, we use a Net::SMTP::SSL connection,
passing its -new all the options that would otherwise go to
Net::SMTP-new (most options) and IO::Socket::SSL-start_SSL (for the
SSL options).
However, while
.
Judging by the name this may be intentional.
Thanks for investigating this.
Duy, you are the expert on the worktree detection logic. Do you know if
there is a reason for --is-inside-work-tree to not honor the
GIT_WORK_TREE / GIT_DIR overrides?
--
Thomas Rast
t...@thomasrast.ch
Duy Nguyen pclo...@gmail.com writes:
On Sun, Dec 1, 2013 at 6:12 PM, Thomas Rast t...@thomasrast.ch wrote:
Øystein Walle oys...@gmail.com writes:
The problem seems to be that git rev-parse --is-inside-work-tree does
not honor these. In fact it doesn't even honor --git-dir or --work-tree
When allocating the slab, the code accidentally computed the array
size from s-slab (an elemtype**). The slab is an array of elemtype*,
however, so we should take the size of *s-slab.
Noticed-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
Signed-off-by: Thomas Rast t...@thomasrast.ch
---
[I hope
1 - 100 of 641 matches
Mail list logo
