Hello ,
I am looking for a reliable supplier /manufacturer of products for sell in
Europe.
I came across your listing and wanted to get some information regarding minimum
Order Quantities, FOB pricing and also the possibility of packaging including
payments terms.
So could you please get
Am 24.02.2018 um 03:24 schrieb Ramsay Jones:
> diff --git a/commit-graph.c b/commit-graph.c
> index fc5ee7e99..c2f443436 100644
> --- a/commit-graph.c
> +++ b/commit-graph.c
> @@ -45,7 +45,7 @@ char *get_graph_latest_filename(const char *obj_dir)
> {
> struct strbuf fname = STRBUF_INIT;
>
On Fri, Feb 23, 2018 at 04:19:54PM -0800, Brandon Williams wrote:
> > We always have the ability to extend the patterns accepted via a feature
> > (or capability) to ls-refs, so maybe the best thing to do now would only
> > support a few patterns with specific semantics. Something like if you
> >
On Thu, Feb 22, 2018 at 04:45:14PM -0800, Brandon Williams wrote:
> > This kind of tail matching can't quite implement all of the current
> > behavior. Because we actually do the normal dwim_ref() matching, which
> > includes stuff like "refs/remotes/%s/HEAD".
> >
> > The other problem with tail-
On Sat, Feb 24, 2018 at 5:29 AM, brian m. carlson
wrote:
>> @@ -40,5 +41,8 @@ int main(int argc, const char **argv)
>>
>> restore_sigpipe_to_default();
>>
>> + if (getenv("GIT_HASH_FIXUP"))
>> + repo_set_hash_algo(the_repository, GIT_HASH_SHA1);
>
> I'm lukewarm on adding thi
After 454253f059 (builtin/index-pack: improve hash function abstraction
- 2018-02-01), index-pack uses the_hash_algo for hashing. If "git
index-pack" is executed without a repository, we do not know what hash
algorithm to be used and the_hash_algo in theory could be undefined.
Since there should b
This is mostly for displaying the hash algorithm name when we report
errors. Printing "unknown" with '%s' is much better than '(null)' in
glibc printf version (and probably could crash if other implementations
do not check for NULL pointer)
Signed-off-by: Nguyễn Thái Ngọc Duy
---
sha1_file.c | 2
Brian questioned the unnecessary alarms in v1 when "git diff" or "git
index-pack" run in no-repository mode. I had the same feeling after
sending v1. But instead of suppresing alarms, we could do better.
v2 breaks those "fall back to SHA-1" code into separate patches and
handles it properly (I hop
Our "git diff" command supports running as a standalone tool. In this
code path, we try to hash the file content but after
18e2588e11 (sha1_file: switch uses of SHA-1 to the_hash_algo -
2018-02-01), there is a chance that the_hash_algo (required by
index_path) may still be uninitialized if no repos
There are many ways for any command to access a git repository:
- most of them will try to discover the .git dir via
setup_git_directory() and friends
- the server side programs already know where the repo is and prepare
with enter_repo()
- special commands that deal with repo creation (init
This reverts commit e26f7f19b6c7485f04234946a59ab8f4fd21d6d1. The root
problem, git clone not setting up the_hash_algo, has been fixed in the
previous patch.
Since this is a dangerous move and could potentially break stuff after
release (and leads to workaround like the reverted commit), the
worka
On Sat, Feb 24, 2018 at 5:17 AM, brian m. carlson
wrote:
> On Fri, Feb 23, 2018 at 04:56:39PM +0700, Nguyễn Thái Ngọc Duy wrote:
>> [3] the reason server side is still running ok with no hash algo
>> before [2] is because the programs that use enter_repo() do very
>> little then spawn a ne
Signed-off-by: Ramsay Jones
---
Hi Derrick,
If you need to re-roll your 'ds/commit-graph' branch, could you
please squash this into the relevant patches (corresponding to
commits 0fd2d95ee6 ["commit-graph: implement --set-latest"],
a33b9b79ff ["commit-graph: implement --delete-expired"] and fin
From: SZEDER Gábor
Commit 2071e05ed2 ("t5536: new test of refspec conflicts when
fetching", 2013-10-30), introduced the verify_stderr() function
which was used to verify that certain fatal/warning messages were
issued by a given git command. In addition, verify_stderr() would
filter a specific "f
Attempting to grep the output of test_i18ngrep will not work under a
poison build, since the output is (almost) guaranteed not to have the
string you are looking for. In this case, we have a test_i18ngrep call
which attempts to filter the contents of a file, which was itself the
result of a call t
Since 'sg/test-i18ngrep' has now graduated to master, unlike v1, these
patches are built on top of current master (@e3a80781f). In addition,
the second patch has been replaced with the patch from SZEDER Gábor[1].
[Hopefully, I have included that patch correctly! If not, please amend
as required.
On Tue, 6 Feb 2018 17:12:58 -0800
Brandon Williams wrote:
> + while ((oid = get_rev())) {
> + packet_buf_write(req_buf, "have %s\n", oid_to_hex(oid));
> + if (++haves_added >= INITIAL_FLUSH)
> + break;
> + };
Unnecessary semicolon after closin
See previous patch for explanation.
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
sha1_file.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index e5fe0aa04ef..f93d3b95b54 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@
See previous patch for explanation.
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
sha1_file.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index f93d3b95b54..8fb56ca0362 100644
--- a/sha1_file.c
+++ b/sha1_f
Add a repository argument to allow the open_sha1_file caller to be
more specific about which repository to act on. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
As with the previous commits, use a macro to catch caller
Add a repository argument to allow the stat_sha1_file caller to be
more specific about which repository to act on. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
As with the previous commits, use a macro to catch caller
Each repository's object store can be initialized independently, so
they must not share a run_once variable.
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
object-store.h | 8 +++-
packfile.c | 7 +++
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/o
Actually this also allows read_info_alternates and link_alt_odb_entry to
handle arbitrary repositories, but link_alt_odb_entries is the most
interesting function in this set of functions, hence the commit subject.
These functions span a strongly connected component in the function
graph, i.e. the
Add a raw_object_store to alt_odb_usable to be more specific about which
repository to act on. The choice of the repository is delegated to its
only caller link_alt_odb_entry.
Signed-off-by: Stefan Beller
---
sha1_file.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
sha1_file.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 952deb02195..73bbe3a3e88 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -897,9 +897,8 @@ static int stat_sha1
See previous patch for explanation.
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
builtin/fsck.c | 2 +-
object-store.h | 3 ++-
packfile.c | 2 +-
sha1_file.c| 13 +++--
sha1_name.c| 2 +-
5 files changed, 12 insertions(+), 10 deletions(-)
diff --git
Add a repository argument to allow the map_sha1_file_1 caller to be
more specific about which repository to act on. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
As with the previous commits, use a macro to catch calle
Signed-off-by: Stefan Beller
---
builtin/am.c | 2 +-
builtin/clone.c| 2 +-
builtin/fetch.c| 2 +-
builtin/merge.c| 2 +-
builtin/receive-pack.c | 2 +-
object.c | 7 +++
packfile.c | 4 ++--
packfile.h | 2 +-
8 files c
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
sha1_file.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 59993a0878d..952deb02195 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -869,23 +869,22 @@ int git_open_cloex
From: Jonathan Nieder
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
sha1_file.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 902cba42106..dfc8deec38e 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -1151,10 +115
Add a repository argument to allow map_sha1_file callers to be more
specific about which repository to handle. This is a small mechanical
change; it doesn't change the implementation to handle repositories
other than the_repository yet.
As with the previous commits, use a macro to catch callers pa
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
object-store.h | 3 +--
sha1_file.c| 4 ++--
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/object-store.h b/object-store.h
index dbd589e0083..8b38330d256 100644
--- a/object-store.h
+++ b/object-store.h
@@ -117,
The approximate_object_count() function maintains a rough count of
objects in a repository to estimate how long object name abbreviates
should be. Object names are scoped to a repository and the
appropriate length may differ by repository, so the object count
should not be global.
Signed-off-by:
Signed-off-by: Stefan Beller
---
object-store.h | 3 +--
sha1_file.c| 12 +---
2 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/object-store.h b/object-store.h
index 08cd48ade11..24b9a750aef 100644
--- a/object-store.h
+++ b/object-store.h
@@ -24,8 +24,7 @@ struct alter
Add a repository argument to allow the link_alt_odb_entry caller to be
more specific about which repository to act on. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
Since the implementation does not yet work with other
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
object-store.h | 3 +--
sha1_file.c| 5 +++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/object-store.h b/object-store.h
index 8b38330d256..afe2f93459b 100644
--- a/object-store.h
+++ b/object-store.h
@@ -119
Add a repository argument to allow sha1_file_name callers to be more
specific about which repository to handle. This is a small mechanical
change; it doesn't change the implementation to handle repositories
other than the_repository yet.
As with the previous commits, use a macro to catch callers p
In a process with multiple repositories open, alternates should be
associated to a single repository and not shared globally. Move
alt_odb_list and alt_odb_tail into the_repository and adjust callers
to reflect this.
Now that the alternative object data base is per repository, we're
leaking its me
Add a repository argument to allow the sha1_loose_object_info caller
to be more specific about which repository to act on. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
As with the previous commits, use a macro to catc
From: Jonathan Nieder
Signed-off-by: Stefan Beller
Signed-off-by: Jonathan Nieder
---
sha1_file.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/sha1_file.c b/sha1_file.c
index 73bbe3a3e88..e32f1da6b69 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -931,10 +931,8 @@
Free the memory and reset alt_odb_{list, tail} to NULL.
Signed-off-by: Stefan Beller
---
object.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/object.c b/object.c
index a2acdee1405..920dc4463fa 100644
--- a/object.c
+++ b/object.c
@@ -446,7 +446,24 @@ void clear_commit_
In a process with multiple repositories open, packfile accessors
should be associated to a single repository and not shared globally.
Move packed_git and packed_git_mru into the_repository and adjust
callers to reflect this.
Patch generated by
1. Moving the struct packed_git declaration to objec
v4:
* addressed feedback from the single patches (mostly nits)
* rebased on latest master
v3:
* reverted back to use the repository for most of the functions
(including unduplicating 'ignore_env')
* rebased on master again (I lost that state when doing v2, as
I did both rebase as well as conve
Migrate the struct alternate_object_database and all its related
functions to the object store as these functions are easier found in
that header. The migration is just a verbatim copy, no need to
include the object store header at any C file, because cache.h includes
repository.h which in turn inc
The raw object store field will contain any objects needed for
access to objects in a given repository.
This patch introduces the raw object store and populates it with the
`objectdir`, which used to be part of the repository struct.
As the struct gains members, we'll also populate the function t
I'm compiling Git with my own static libcurl and my own static
LibreSSL. They live in two different locations.
Building Curl with a pointer to my LibreSSL works fine, and compiling
Git works fine: the correct -I options are added to the compile line
when I configure with --with-openssl=/path/to/l
On Thu, Feb 22, 2018 at 4:10 AM,
wrote:
> Hello,
> I've found an issue in git when working with submodules.
> My Project is set up using hundreds of components by submodules (and
> nested submodules), that are independent created in central development
> groups.
> Now it occurs that the structure
On 02/22, Brandon Williams wrote:
> On 02/22, Jeff King wrote:
> > On Tue, Feb 06, 2018 at 05:12:50PM -0800, Brandon Williams wrote:
> >
> > > +ls-refs takes in the following parameters wrapped in packet-lines:
> > > +
> > > +symrefs
> > > + In addition to the object pointed by it, show the un
Junio C Hamano writes:
> Paul-Sebastian Ungureanu writes:
>
>> Basically, the option parser only parses strings that represent
>> commits and the ref-filter performs the commit look-up. If an
>> error occurs during the option parsing, then it must be an invalid
>> argument and the user should be
Three "missing reference" tests in 't5500-fetch-pack.sh' fail when the
test script is run with '-x' tracing (and using a shell other than a
Bash version supporting BASH_XTRACEFD). The reason for those failures
is that the tests check a subshell's stderr, which includes the trace
of executing comma
The test 'no-op fetch without "-v" is quiet' in 't5570-git-daemon.sh'
fails when the test script is run with '-x' tracing (and using a shell
other than a Bash version supporting BASH_XTRACEFD). The reason for
the failure is that the test checks the emptiness of a subshell's
stderr, which includes
A test in 't9903-bash-prompt.sh' fails when the test script is run
with '-x' tracing and a Bash version not yet supporting BASH_XTRACEFD,
notably the default Bash version shipped in OSX. The reason for the
failure is that the test checks the emptiness of __git_ps1()'s stderr,
which includes the tr
't1510-repo-setup.sh' checks the stderr of nested function calls way
too many times, resulting in several failures when using '-x' tracing,
unless it's executed with a Bash version supporting BASH_XTRACEFD.
Maybe someday we will clear up this test script, but until then mark
it as 'test_untraceabl
The two test checking 'git mmerge-recursive' in an empty worktree in
't3030-merge-recursive.sh' fail when the test script is run with '-x'
tracing (and using a shell other than a Bash version supporting
BASH_XTRACEFD). The reason for those failures is that the tests check
the emptiness of a subshe
Three tests in 't1507-rev-parse-upstream.sh' fail when the test script
is run with '-x' tracing (and using a shell other than a Bash version
supporting BASH_XTRACEFD). The reason for those failures is that the
tests check the stderr of the function 'error_message', which includes
the trace of comm
Now that the test suite runs successfully with '-x' tracing even with
/bin/sh, enable it on Travis CI in order to
- get more information about test failures, and
- catch constructs breaking '-x' with /bin/sh sneaking into our test
suite.
Signed-off-by: SZEDER Gábor
---
ci/lib-travisci.
The test 'fetch --recurse-submodules -j2 has the same output
behaviour' in 't5526-fetch-submodules.sh' fails when the test script
is run with '-x' tracing (and using a shell other than a Bash version
supporting BASH_XTRACEFD). The reason of that failure is the
following command:
GIT_TRACE=$(pwd
Explain in 't/README' why it is a bad idea to redirect and verify the
stderr of compound commands, in the hope that future contributions
will follow this advice and the test suite will keep working with '-x'
tracing and /bin/sh.
While at it, since we can now run the test suite with '-x' without
ne
Running a test script with '-x' turns on 'set -x' tracing, the output
of which is normally sent to stderr. This causes a lot of
test failures, because many tests redirect and verify the stderr
of shell functions, most frequently that of 'test_must_fail'.
These issues were worked around somewhat in
The previous patch resolved most of the test failures caused by
running our test suite with '-x' tracing and /bin/sh, and the
following patches in this series will resolve almost all of the
remaining failures. Unfortunately, not yet all.
Add means to disable '-x' tracing for individual test scrip
This patch series makes '-x' tracing of tests work reliably even when
running them with /bin/sh, and setting TEST_SHELL_PATH=bash will be
unnecessary.
make GIT_TEST_OPTS='-x --verbose-log' test
passes on my setup and on all Travis CI build jobs (though neither me
nor Travis CI run all tests, e.
On Fri, Feb 9, 2018 at 3:21 PM, Jeff King wrote:
> On Fri, Feb 09, 2018 at 03:42:34AM +0100, SZEDER Gábor wrote:
>
>> To check that a git command fails and to inspect its error message we
>> usually execute a command like this throughout our test suite:
>>
>> test_must_fail git command --option
On Wed, Feb 21, 2018 at 4:35 PM, Jonathan Tan wrote:
> On Tue, 20 Feb 2018 17:54:18 -0800
> Stefan Beller wrote:
>
>> -void prepare_alt_odb_the_repository(void)
>> +void prepare_alt_odb(struct repository *r)
>> {
>> - const char *alt;
>> -
>> - if (the_repository->objects.alt_odb_tail)
>
On 02/23, brian m. carlson wrote:
> On Fri, Feb 23, 2018 at 04:56:40PM +0700, Nguyễn Thái Ngọc Duy wrote:
> > diff --git a/builtin/index-pack.c b/builtin/index-pack.c
> > index 7e3e1a461c..8ee935504e 100644
> > --- a/builtin/index-pack.c
> > +++ b/builtin/index-pack.c
> > @@ -1673,6 +1673,11 @@ int
On 02/23, Stefan Beller wrote:
> On Wed, Feb 21, 2018 at 4:51 PM, Brandon Williams wrote:
> > On 02/20, Stefan Beller wrote:
> >> Add a repository argument to allow sha1_file_name callers to be more
> >> specific about which repository to handle. This is a small mechanical
> >> change; it doesn't
On 02/23, Stefan Beller wrote:
> On Fri, Feb 23, 2018 at 1:30 PM, Brandon Williams wrote:
> > On 02/22, Stefan Beller wrote:
> >> > +static enum protocol_version discover_version(struct packet_reader
> >> > *reader)
> >> > +{
> >> ...
> >> > +
> >> > + /* Maybe process capabilities here, at
Am 23.02.2018 um 23:17 schrieb Junio C Hamano:
> René Scharfe writes:
>
>> +#define IGNORE_ERROR(expr) do { int e_ = errno; expr; errno = e_; } while
>> (0)
>
> The macro certainly is a cute idea, but ...
>
>> @@ -391,7 +393,7 @@ ssize_t strbuf_read(struct strbuf *sb, int fd, size_t
>> hint)
On Wed, Feb 21, 2018 at 4:44 PM, Jonathan Tan wrote:
> On Tue, 20 Feb 2018 17:54:25 -0800
> Stefan Beller wrote:
>
>> Signed-off-by: Stefan Beller
>> Signed-off-by: Jonathan Nieder
>
> Reviewed-by: Jonathan Tan
>
>> -void sha1_file_name_the_repository(struct strbuf *buf, const unsigned char
>
On Fri, Feb 23, 2018 at 04:56:38PM +0700, Nguyễn Thái Ngọc Duy wrote:
> I can certainly try! I start to remember all the hairy details in that
> setup code.
>
> The first step may be something like this, which identifies all the
> "repo init" entry points. This is basically a revert of e26f7f19b6
Stephen R Guglielmo writes:
> If log.showsignature is true (or --show-signature is passed) while
> performing a `subtree add` or `subtree pull`, the command fails.
>
> toptree_for_commit() calls `log` and passes the output to `commit-tree`.
> If this output shows the GPG signature data, `commit-t
On Wed, Feb 21, 2018 at 4:51 PM, Brandon Williams wrote:
> On 02/20, Stefan Beller wrote:
>> Add a repository argument to allow sha1_file_name callers to be more
>> specific about which repository to handle. This is a small mechanical
>> change; it doesn't change the implementation to handle repos
>> --- a/sha1_file.c
>> +++ b/sha1_file.c
>> @@ -23,6 +23,7 @@
>> #include "sha1-lookup.h"
>> #include "bulk-checkin.h"
>> #include "repository.h"
>> +#include "object-store.h"
>
> Should this #include have been added in an earlier patch, since the
> file both uses and defines prepare_alt_odb, w
On Fri, Feb 23, 2018 at 04:56:40PM +0700, Nguyễn Thái Ngọc Duy wrote:
> diff --git a/builtin/index-pack.c b/builtin/index-pack.c
> index 7e3e1a461c..8ee935504e 100644
> --- a/builtin/index-pack.c
> +++ b/builtin/index-pack.c
> @@ -1673,6 +1673,11 @@ int cmd_index_pack(int argc, const char **argv, c
"Bernhard M. Wiedemann" writes:
> amazingly timegm(gmtime(0)) is only 0 before 2020
> because perl's timegm deviates from GNU timegm(3) in how it handles years.
>
> man Time::Local says
>
> Whenever possible, use an absolute four digit year instead.
>
> with a detailed explanation about ambiguit
Stefan Beller writes:
> On Fri, Feb 23, 2018 at 11:50 AM, Junio C Hamano wrote:
>> Stefan Beller writes:
>>
>>> I wonder if there is yet another missing case in the enumeration of
>>> the previous patch:
>>> Some commands are able to operate on GIT_OBJECT_DIR instead
>>> of GIT_DIR (git repack?
On Wed, Feb 21, 2018 at 4:47 PM, Brandon Williams wrote:
> On 02/20, Stefan Beller wrote:
>> The approximate_object_count() function maintains a rough count of
>> objects in a repository to estimate how long object name abbreviates
>> should be. Object names are scoped to a repository and the
>>
On Fri, Feb 23, 2018 at 04:56:39PM +0700, Nguyễn Thái Ngọc Duy wrote:
> [3] the reason server side is still running ok with no hash algo
> before [2] is because the programs that use enter_repo() do very
> little then spawn a new program (like pack-objects or
> upload-archive) to do the
René Scharfe writes:
> +#define IGNORE_ERROR(expr) do { int e_ = errno; expr; errno = e_; } while (0)
The macro certainly is a cute idea, but ...
> @@ -391,7 +393,7 @@ ssize_t strbuf_read(struct strbuf *sb, int fd, size_t
> hint)
>
> if (got < 0) {
> if (o
On Fri, Feb 23, 2018 at 1:30 PM, Brandon Williams wrote:
> On 02/22, Stefan Beller wrote:
>> > +static enum protocol_version discover_version(struct packet_reader
>> > *reader)
>> > +{
>> ...
>> > +
>> > + /* Maybe process capabilities here, at least for v2 */
>> > + switch (version)
On 02/22, Jeff King wrote:
> On Tue, Feb 06, 2018 at 05:12:49PM -0800, Brandon Williams wrote:
>
> > +In protocol v2 communication is command oriented. When first contacting a
> > +server a list of capabilities will advertised. Some of these capabilities
> > +will be commands which a client can
>> 2. Applying the semantic patch
>> contrib/coccinelle/refactoring/packed_git.cocci to adjust callers.
>> This semantic patch is placed in a sub directory of the coccinelle
>> contrib dir, as this semantic patch is not expected to be of general
>> usefulness; it is only useful dur
On 02/21, Jonathan Tan wrote:
> On Tue, 6 Feb 2018 17:12:49 -0800
> Brandon Williams wrote:
>
> > .gitignore | 1 +
> > Documentation/technical/protocol-v2.txt | 114 +++
> > Makefile| 2 +
> > builtin.h
On 02/22, Stefan Beller wrote:
> > +static enum protocol_version discover_version(struct packet_reader *reader)
> > +{
> ...
> > +
> > + /* Maybe process capabilities here, at least for v2 */
> > + switch (version) {
> > + case protocol_v1:
> > + /* Read the peeked v
Phillip Wood writes:
> It would certainly be nice to be able to share branch descriptions so
> that if I clone a repository I can get a bit more detail about the ideas
> behind each branch. Shared descriptions could be displayed in web uis. I
One thing to note is that there is no universal ident
On 02/22, Stefan Beller wrote:
> On Tue, Feb 6, 2018 at 5:12 PM, Brandon Williams wrote:
>
> > +static void pack_line(const char *line)
> > +{
> > + if (!strcmp(line, "") || !strcmp(line, "\n"))
>
> From our in-office discussion:
> v1/v0 packs pktlines twice in http, which is not p
Ævar Arnfjörð Bjarmason writes:
>> Let's see how others find it useful and/or if the changed code gets
>> in the way of others (I am not absolutely sure if the changes are
>> free of regression to existing users who do not use the new
>> feature).
>
> I think if you're on the fence about merging
On 02/22, Jeff King wrote:
> On Thu, Feb 22, 2018 at 03:19:40PM -0500, Jeff King wrote:
>
> > > To be clear, which of the following are you (most) worried about?
> > >
> > > 1. being invoked with --help and spawning a pager
> > > 2. receiving and acting on options between 'git' and 'upload-pack
On Wed, Feb 21, 2018 at 4:31 PM, Junio C Hamano wrote:
> * en/rename-directory-detection (2018-02-14) 29 commits
> - merge-recursive: ensure we write updates for directory-renamed file
> - merge-recursive: avoid spurious rename/rename conflict from dir renames
> - directory rename detection: ne
Am 23.02.2018 um 08:00 schrieb Jeff King:
> On Fri, Feb 23, 2018 at 01:49:52AM -0500, Jeff King wrote:
> Subject: [PATCH] strbuf_read_file(): preserve errno across close() call
>
> If we encounter a read error, the user may want to report it
> by looking at errno. However, our close() call may clo
Paul-Sebastian Ungureanu writes:
> Hello,
> I have made the changes after review. This is the updated patch
> based on what was discussed last time [1].
>
> In this patch, I have fixed the same issue that was also seen
> in "git branch" and "git for-reach-ref". I have also removed the
> dead code
If log.showsignature is true (or --show-signature is passed) while
performing a `subtree add` or `subtree pull`, the command fails.
toptree_for_commit() calls `log` and passes the output to `commit-tree`.
If this output shows the GPG signature data, `commit-tree` throws a
fatal error.
This commit
Julius Musseau writes:
> I'm embarrassed to realise your approach matches the top-voted
> stack-overflow answer on the subject:
> https://stackoverflow.com/a/5201642
I personally do not visit stack-overflow, but I am happy to see that
there are people who remember "right" way to do this among th
Junio C Hamano writes:
> Lars Schneider writes:
>
>> I still think it would be nice to see diffs for arbitrary encodings.
>> Would it be an option to read the `encoding` attribute and use it in
>> `git diff`?
>
> Reusing that gitk-only thing and suddenly start doing so would break
> gitk users,
On Fri, Feb 23, 2018 at 11:50 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> I wonder if there is yet another missing case in the enumeration of
>> the previous patch:
>> Some commands are able to operate on GIT_OBJECT_DIR instead
>> of GIT_DIR (git repack?), which may not even explore th
On 2/23/2018 2:30 PM, Junio C Hamano wrote:
Derrick Stolee writes:
jt/binsearch-with-fanout introduces one when there is a 256-entry
fanout table (not the case here).
The bsearch() method in search.h (and used in
pack-write.c:need_large_offset) does not return the _position_ of a
found elem
On Wed, Feb 21, 2018 at 1:51 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> +
>> +/*
>> + * The mru list_head is supposed to be initialized using
>> + * the LIST_HEAD macro, assigning prev/next to itself.
>> + * However this doesn't work in this case as some compilers dislike
>> + * that
On 02/23, Jonathan Tan wrote:
> On Tue, 6 Feb 2018 17:13:00 -0800
> Brandon Williams wrote:
>
> > @@ -1090,6 +1110,10 @@ static int send_fetch_request(int fd_out, const
> > struct fetch_pack_args *args,
> > if (prefer_ofs_delta)
> > packet_buf_write(&req_buf, "ofs-delta");
> >
Derrick Stolee writes:
> My thought was that using a fixed name
> (e.g. .git/objects/info/commit-graph) would block making the graph
> incremental. Upon thinking again, this is not the case. That feature
> could be designed with a fixed name for the small, frequently-updated
> file and use .../in
Stefan Beller writes:
> I wonder if there is yet another missing case in the enumeration of
> the previous patch:
> Some commands are able to operate on GIT_OBJECT_DIR instead
> of GIT_DIR (git repack?), which may not even explore the full git directory,
> and so doesn't know about the hash value
Junio C Hamano writes:
>> I think the current name makes the following call very clear:
>
> It is still a strange name nevertheless.
Sorry for simply repeating "strange" without spelling out why in the
previous message. This certainly is subjective and depends on your
cultural background, but i
1 - 100 of 160 matches
Mail list logo