Brandon Williams wrote:
> Construct a list of ref patterns to be passed to
> 'transport_get_remote_refs()' from the refspec to be used during the
> fetch. This list of ref patterns will be used to allow the server to
> filter the ref advertisement when communicating using protocol v2.
>
> Signed-
Brandon Williams wrote:
> Teach the client to be able to request a remote's refs using protocol
> v2. This is done by having a client issue a 'ls-refs' request to a v2
> server.
Yay, ls-remote support!
[...]
> --- a/builtin/upload-pack.c
> +++ b/builtin/upload-pack.c
> @@ -5,6 +5,7 @@
> #inclu
Jonathan Tan wrote:
> On Thu, 22 Feb 2018 13:26:58 -0500
> Jeff King wrote:
>> I agree that it shouldn't matter much here. But if the name argv_array
>> is standing in the way of using it, I think we should consider giving it
>> a more general name. I picked that not to evoke "this must be argume
Hi,
Brandon Williams wrote:
> Introduce protocol_v2, a new value for 'enum protocol_version'.
> Subsequent patches will fill in the implementation of protocol_v2.
>
> Signed-off-by: Brandon Williams
> ---
Yay!
[...]
> +++ b/builtin/fetch-pack.c
> @@ -201,6 +201,9 @@ int cmd_fetch_pack(int argc
Jonathan Nieder wrote:
> Brandon Williams wrote:
>> Sometimes it is advantageous to be able to peek the next packet line
>> without consuming it (e.g. to be able to determine the protocol version
>> a server is speaking). In order to do that introduce 'struct
>> packet_reader' which is an abstrac
Brandon Williams wrote:
> Remove code duplication and use the existing 'get_refs_via_connect()'
> function to retrieve a remote's heads in 'fetch_refs_via_pack()' and
> 'git_transport_push()'.
>
> Signed-off-by: Brandon Williams
> ---
> transport.c | 18 --
> 1 file changed, 4 i
The USA Internet Command Protocol promotions has selected your e-mail ID as
lucky winner of US$2,500.000 out of US$350,000.000.00 shared worldwide for
150.000 internet e-mail users.
Your Winning Code is (youripnews763-alertenews-abc-2.5m$$$@)
For your payment, quickly forward your email winning
Hi,
Brandon Williams wrote:
> Sometimes it is advantageous to be able to peek the next packet line
> without consuming it (e.g. to be able to determine the protocol version
> a server is speaking). In order to do that introduce 'struct
> packet_reader' which is an abstraction around the normal p
Hi Duy,
Duy Nguyen wrote:
> On Fri, Jan 26, 2018 at 6:58 AM, Brandon Williams wrote:
>> + stateless-rpc
>> +---
>> +
>> +If advertised, the `stateless-rpc` capability indicates that the server
>> +supports running commands in a stateless-rpc mode, which means that a
>> +command lasts
On Mon, Feb 26, 2018 at 4:07 PM, Johannes Schindelin
wrote:
> Hi Buga,
>
> On Tue, 20 Feb 2018, Igor Djordjevic wrote:
>
>> I`m really interested in this topic, which seems to (try to) address the
>> only "bad feeling" I had with rebasing merges - being afraid of silently
>> losing amendments by a
On Sun, Feb 25, 2018 at 6:35 AM, Lars Schneider
wrote:
>> On 25 Feb 2018, at 04:41, Eric Sunshine wrote:
>> Is this interpretation correct? When I read [1], I interpret it as
>> saying that no BOM _of any sort_ should be present when the encoding
>> is declared as one of UTF-16BE, UTF-16LE, UTF-3
Ævar Arnfjörð Bjarmason wrote:
> On Sat, Feb 24 2018, Jeff King jotted:
>> I actually wonder if we should just specify that the patterns must
>> _always_ be fully-qualified, but may end with a single "/*" to iterate
>> over wildcards. Or even simpler, that "refs/heads/foo" would find that
>> ref i
Hi Johannes,
Johannes Schindelin writes:
> Hi Buga,
>
> On Tue, 20 Feb 2018, Igor Djordjevic wrote:
>
>> I`m really interested in this topic, which seems to (try to) address the
>> only "bad feeling" I had with rebasing merges - being afraid of silently
>> losing amendments by actually trying to
When useClientSpec=true, stripping of P4 depot paths doesn't happen
correctly on sync. Modifies stripRepoPath to handle this case better.
Signed-off-by: Nuno Subtil
---
git-p4.py | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/git-p4.py b/git-p4.py
index 7bb9cadc
Teach write_commit_graph() to walk all parents from the commits
discovered in packfiles. This prevents gaps given by loose objects or
previously-missed packfiles.
Also automatically add commits from the existing graph file, if it
exists.
Signed-off-by: Derrick Stolee
---
commit-graph.c | 23 +++
The commit graph feature is controlled by the new core.commitGraph config
setting. This defaults to 0, so the feature is opt-in.
The intention of core.commitGraph is that a user can always stop checking
for or parsing commit graph files if core.commitGraph=0.
Signed-off-by: Derrick Stolee
---
D
Teach git-commit-graph to read commit graph files and summarize their contents.
Use the read subcommand to verify the contents of a commit graph file in the
tests.
Signed-off-by: Derrick Stolee
---
Documentation/git-commit-graph.txt | 12
builtin/commit-graph.c | 56 +
Add Documentation/technical/commit-graph.txt with details of the planned
commit graph feature, including future plans.
Signed-off-by: Derrick Stolee
---
Documentation/technical/commit-graph.txt | 164 +++
1 file changed, 164 insertions(+)
create mode 100644 Documenta
Teach Git to inspect a commit graph file to supply the contents of a
struct commit when calling parse_commit_gently(). This implementation
satisfies all post-conditions on the struct commit, including loading
parents, the root tree, and the commit date.
If core.commitGraph is false, then do not ch
This patch series is another big difference from version 4, but I do
think we are converging on a stable design.
This series depends on a few things in flight:
* jt/binsearch-with-fanout for bsearch_graph()
* 'master' includes the sha1file -> hashfile rename in (98a3beab).
* [PATCH] commit: dr
Teach Git to write a commit graph file by checking all packed objects
to see if they are commits, then store the file in the given object
directory.
Signed-off-by: Derrick Stolee
---
Makefile | 1 +
commit-graph.c | 360 +
commit-gr
Teach git-commit-graph to inspect the objects only in a certain list
of pack-indexes within the given pack directory. This allows updating
the commit graph iteratively.
Signed-off-by: Derrick Stolee
---
Documentation/git-commit-graph.txt | 11 ++-
builtin/commit-graph.c | 33
Teach git-commit-graph to add all commits from the existing
commit-graph file to the file about to be written. This should be
used when adding new commits without performing garbage collection.
Signed-off-by: Derrick Stolee
---
Documentation/git-commit-graph.txt | 10 ++
builtin/commit-g
Teach git-commit-graph to read commits from stdin when the
--stdin-commits flag is specified. Commits reachable from these
commits are added to the graph. This is a much faster way to construct
the graph than inspecting all packed objects, but is restricted to
known tips.
For the Linux repository,
Thanks for the help in getting all the details right in setting up a
builtin.
-- >8 --
Teach git the 'commit-graph' builtin that will be used for writing and
reading packed graph files. The current implementation is mostly
empty, except for an '--object-dir' option.
Signed-off-by: Derrick Stolee
Teach git-commit-graph to write graph files. Create new test script to verify
this command succeeds without failure.
Signed-off-by: Derrick Stolee
---
Documentation/git-commit-graph.txt | 39
builtin/commit-graph.c | 33 ++
t/t5318-commit-graph.sh|
Add document specifying the binary format for commit graphs. This
format allows for:
* New versions.
* New hash functions and hash lengths.
* Optional extensions.
Basic header information is followed by a binary table of contents
into "chunks" that include:
* An ordered list of commit object IDs
This patch is new to the series due to the interactions with the lockfile API
and the hashfile API. I need to ensure the hashfile writes the hash value at
the end of the file, but keep the file descriptor open so the lock is valid.
I welcome any susggestions to this patch or to the way I use it in
On Mon, Feb 26, 2018 at 06:25:24PM +0700, Duy Nguyen wrote:
> On Mon, Feb 26, 2018 at 4:11 AM, brian m. carlson
> wrote:
> > @@ -44,7 +44,7 @@ void resolve_undo_write(struct strbuf *sb, struct
> > string_list *resolve_undo)
> > for (i = 0; i < 3; i++) {
> >
Hello, I recently noticed a bug involving GitBash and Python. I was
running a function that would post the system time once every second
using a while loop but the text was only sent after the while loop
ended due to a timer I had set. Essesntially, instead of it being
entered every second into the
On Tue, Feb 27, 2018 at 3:30 AM, Stefan Beller wrote:
>> diff --git a/setup.c b/setup.c
>> index c5d55dcee4..6fac1bb58a 100644
>> --- a/setup.c
>> +++ b/setup.c
>> @@ -1116,8 +1116,7 @@ const char *setup_git_directory_gently(int *nongit_ok)
>> const char *gitdir = getenv(GI
On Tue, Feb 27, 2018 at 3:46 AM, Stefan Beller wrote:
> What is the plan from here on?
> Should I build further series on top of yours? The next series will
> focus on the pack side of things (pack.h, packfile.{c,h})
>
> So maybe we'll have Junio merge down my series (and yours as it
> needs one r
Hi Buga,
On Tue, 20 Feb 2018, Igor Djordjevic wrote:
> I`m really interested in this topic, which seems to (try to) address the
> only "bad feeling" I had with rebasing merges - being afraid of silently
> losing amendments by actually trying to "replay" the merge (where
> additional and possibly
On Tue, Feb 27, 2018 at 3:50 AM, Stefan Beller wrote:
>> The natural thing to do is move these to raw_object_store too (and
>> repo_submodule_init needs to check submodule's config file). But one
>> may argue these should be per-process instead of per-repo though. I
>> don't know. But I thought I
On Sat, Feb 24 2018, Jeff King jotted:
> On Thu, Feb 22, 2018 at 04:45:14PM -0800, Brandon Williams wrote:
>> > Does the client have to be aware that we're using wildmatch? I think
>> > they'd need "refs/heads/**" to actually implement what we usually
>> > specify in refspecs as "refs/heads/*". O
On Tue, Feb 27, 2018 at 2:28 AM, Stefan Beller wrote:
> On Mon, Feb 26, 2018 at 1:30 AM, Duy Nguyen wrote:
>> On Fri, Feb 23, 2018 at 04:47:28PM -0800, Stefan Beller wrote:
>>> /* The main repository */
>>> static struct repository the_repo = {
>>> - NULL, NULL, NULL, NULL, NULL, NULL, NULL
On Mon, Feb 26, 2018 at 6:48 AM, Luke Diamand wrote:
> It takes a list of P4 changelists and generates a patch for
> each one, using "p4 describe".
> [...]
> Signed-off-by: Luke Diamand
> ---
> diff --git a/git-p4.py b/git-p4.py
> @@ -3749,6 +3761,277 @@ class P4Branches(Command):
> +class P4Make
Hi Peff,
On Fri, 23 Feb 2018, Jeff King wrote:
> On Fri, Feb 23, 2018 at 06:29:55AM +0100, "Marcel 'childNo͡.de' Trautwein"
> wrote:
>
> > shows me a quite different behavior, so solely rebase not seems the
> > full problem BUT `--rebase=preserve` will .. o’man , really, is this
> > intended?
>
very nice subcommand, I tested it with a shelved CL and a submitted CL.
Find my comments inline
On Mon, Feb 26, 2018 at 12:48 PM, Luke Diamand wrote:
> It takes a list of P4 changelists and generates a patch for
> each one, using "p4 describe".
>
> This is especially useful for applying shelved c
Hi Junio,
On Fri, 23 Feb 2018, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > On Wed, 21 Feb 2018, Junio C Hamano wrote:
> >
> >> * js/rebase-recreate-merge (2018-02-12) 12 commits
> >> ...
> >>
> >> "git rebase" learned "--recreate-merges" to transplant the whole
> >> topology o
Duy Nguyen writes:
> Yes that's the intention. But after writing cover letter for v2 and
> sending it out, it looks to me that this thing must stay until all our
> code is converted to using the_hash_algo (I don't know if there are
> more to convert or it's finished already). So an alternative is
Jeff King writes:
> I actually wonder if we should just specify that the patterns must
> _always_ be fully-qualified, but may end with a single "/*" to iterate
> over wildcards. Or even simpler, that "refs/heads/foo" would find that
> ref itself, and anything under it.
>
> That drops any question
On 02/23, Jonathan Tan wrote:
> 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;
> > + };
This one is a bit tricky to explain, so let's try with a diagram:
C
/ \
A - B - E - F
\ /
D
To illustrate what this new mode is all about, let's consider what
happens upon `git rebase -i --recreate-merges B`, in particular to
the commit `D`. So far, the new branch structur
There are some commands that have to be skipped from rearranging by virtue
of not handling any commits.
However, the logic was not quite obvious: it skipped commands based on
their position in the enum todo_command.
Instead, let's make it explicit that we skip all commands that do not
handle any
Similar to the `preserve` mode simply passing the `--preserve-merges`
option to the `rebase` command, the `recreate` mode simply passes the
`--recreate-merges` option.
This will allow users to conveniently rebase non-trivial commit
topologies when pulling new commits, without flattening them.
Sig
In the previous patches, we implemented the basic functionality of the
`git rebase -i --recreate-merges` command, in particular the `merge`
command to create merge commits in the sequencer.
The interactive rebase is a lot more these days, though, than a simple
cherry-pick in a loop. For example, i
Once upon a time, this here developer thought: wouldn't it be nice if,
say, Git for Windows' patches on top of core Git could be represented as
a thicket of branches, and be rebased on top of core Git in order to
maintain a cherry-pick'able set of patch series?
The original attempt to answer this
This allows for rebases to be run in parallel in separate worktrees
(think: interrupted in the middle of one rebase, being asked to perform
a different rebase, adding a separate worktree just for that job).
Signed-off-by: Johannes Schindelin
---
refs.c| 3 ++-
t/t343
In the upcoming commits, we will teach the sequencer to recreate merges.
This will be done in a very different way from the unfortunate design of
`git rebase --preserve-merges` (which does not allow for reordering
commits, or changing the branch topology).
The main idea is to introduce new todo li
This patch is part of the effort to reimplement `--preserve-merges` with
a substantially improved design, a design that has been developed in the
Git for Windows project to maintain the dozens of Windows-specific patch
series on top of upstream Git.
The previous patch implemented the `label` and `
From: Stefan Beller
Up to now each command took a commit as its first argument and ignored
the rest of the line (usually the subject of the commit)
Now that we are about to introduce commands that take different
arguments, clarify each command by giving the argument list.
Signed-off-by: Stefan
The sequencer just learned new commands intended to recreate branch
structure (similar in spirit to --preserve-merges, but with a
substantially less-broken design).
Let's allow the rebase--helper to generate todo lists making use of
these commands, triggered by the new --recreate-merges option. Fo
Just like with regular `pick` commands, if we are trying to recreate a
merge commit, we now test whether the parents of said commit match HEAD
and the commits to be merged, and fast-forward if possible.
This is not only faster, but also avoids unnecessary proliferation of
new objects.
Signed-off-
Once upon a time, I dreamt of an interactive rebase that would not
flatten branch structure, but instead recreate the commit topology
faithfully.
My original attempt was --preserve-merges, but that design was so
limited that I did not even enable it in interactive mode.
Subsequently, it *was* ena
As pointed out in a review of the `--recreate-merges` patch series,
`rollback_lock_file()` clobbers errno. Therefore, we have to report the
error message that uses errno before calling said function.
Signed-off-by: Johannes Schindelin
---
sequencer.c | 13 -
1 file changed, 8 inserti
On 25 February 2018 at 04:48, Kaartic Sivaraam
wrote:
> On Wednesday 21 February 2018 02:14 AM, Martin Ågren wrote:
>> To sum up: I probably won't be looking into Travis-ing such a blacklist
>> in the near future.
>>
>
> Just thinking out loud, how about having a white-list instead of a
> black-li
On Mon, Feb 26, 2018 at 12:55 AM, Jeff King wrote:
> On Fri, Feb 23, 2018 at 02:22:14PM -0800, Stefan Beller wrote:
>
>> >> + /*
>> >> + * A fast, rough count of the number of objects in the repository.
>> >> + * These two fields are not meant for direct access. Use
>> >> + * ap
On Sat, Feb 24, 2018 at 7:00 AM, Duy Nguyen wrote:
> I notice that there are a few global state (or configuration rather)
> left after this: packed_git_window_size, packed_git_limit and
> delta_base_cache_limit. These can be changed by $GIT_DIR/config, but
> since it's still global, a submodule re
Hi Jake,
On Sun, 25 Feb 2018, Jacob Keller wrote:
> On Fri, Feb 23, 2018 at 4:35 AM, Johannes Schindelin
> wrote:
> > Changes since v3:
> >
> > - fixed a grammar error in "introduce the `merge` command"'s commit message.
> >
> > - fixed a couple of resource leaks in safe_append() and do_reset(),
On Mon, Feb 26, 2018 at 06:35:33PM +0100, Torsten Bögershausen wrote:
> > diff --git a/userdiff.c b/userdiff.c
> > index dbfb4e13cd..48fa7e8bdd 100644
> > --- a/userdiff.c
> > +++ b/userdiff.c
> > @@ -161,6 +161,7 @@ IPATTERN("css",
> > "-?[_a-zA-Z][-_a-zA-Z0-9]*" /* identifiers */
> > "
On Mon, Feb 26, 2018 at 2:30 AM, Nguyễn Thái Ngọc Duy wrote:
> It turns out I don't need my other series [1] in order to delete this
> field. This series moves getenv() calls from
> repo_set_gitdir()/repo_setup_env() and prepare_alt_odb() back in
> environment.c where they belong in my opinion.
>
On Mon, Feb 26, 2018 at 09:56:47AM -0500, Derrick Stolee wrote:
> diff --git a/sha1_name.c b/sha1_name.c
> index 611c7d2..44dd595 100644
> --- a/sha1_name.c
> +++ b/sha1_name.c
> @@ -546,17 +546,12 @@ static void find_abbrev_len_for_pack(struct packed_git
> *p,
>* nearby for the abbreviat
> diff --git a/setup.c b/setup.c
> index c5d55dcee4..6fac1bb58a 100644
> --- a/setup.c
> +++ b/setup.c
> @@ -1116,8 +1116,7 @@ const char *setup_git_directory_gently(int *nongit_ok)
> const char *gitdir = getenv(GIT_DIR_ENVIRONMENT);
> if (!gitdir)
>
On Mon, Feb 26, 2018 at 1:30 AM, Duy Nguyen wrote:
> On Fri, Feb 23, 2018 at 04:47:28PM -0800, Stefan Beller wrote:
>> /* The main repository */
>> static struct repository the_repo = {
>> - NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, &the_index,
>> &hash_algos[GIT_HASH_SHA1], 0,
On Sun, Feb 25, 2018 at 12:34 PM, brian m. carlson
wrote:
> On Sun, Feb 25, 2018 at 06:18:34PM +0700, Nguyễn Thái Ngọc Duy wrote:
>> v3 refines v2 a bit more:
>>
>> - fix configure typo (and stray words in commit message)
>> - use repo_set_hash_algo() instead of reassigning the_hash_algo
>> - comp
On Mon, Feb 26, 2018 at 5:30 AM, Nguyễn Thái Ngọc Duy wrote:
> It does not make sense that generic repository code contains handling
> of environment variables, which are specific for the main repository
> only. Refactor repo_set_gitdir() function to take $GIT_DIR and
> optionally _all_ other cust
tbo...@web.de:
+static inline int buffer_has_utf16_bom(const void *buf, size_t len) {
+ const unsigned char *text = (unsigned char *)buf;
+ if (!text || len < 2)
+return 0;
+ if (text[0] == 0xff && text[1] == 0xfe)
+return 1;
+ if (text[0] == 0xfe && text[1] == 0xff)
+return 1;
On 02/26, Junio C Hamano wrote:
> Duy Nguyen writes:
>
> > diff --git a/common-main.c b/common-main.c
> > index 6a689007e7..a13ab981aa 100644
> > --- a/common-main.c
> > +++ b/common-main.c
> > @@ -1,6 +1,7 @@
> > #include "cache.h"
> > #include "exec_cmd.h"
> > #include "attr.h"
> > +#include
Duy Nguyen writes:
> diff --git a/common-main.c b/common-main.c
> index 6a689007e7..a13ab981aa 100644
> --- a/common-main.c
> +++ b/common-main.c
> @@ -1,6 +1,7 @@
> #include "cache.h"
> #include "exec_cmd.h"
> #include "attr.h"
> +#include "repository.h"
>
> /*
> * Many parts of Git have
On Fri, 23 Feb 2018 16:47:27 -0800
Stefan Beller wrote:
> v4:
> * addressed feedback from the single patches (mostly nits)
> * rebased on latest master
The patches I looked at previously (patches 7, 15, 19, 22, and 24) look
good to me.
Nguyễn Thái Ngọc Duy writes:
> This series is built on top of Stefan's object-store-part1, v4. I
> could rebase it on 'master' too, but then Junio may need to resolve
> some conflicts.
As a follow-up fix for combined "move things to the_repo as much as
possible" efforts I think what you did mak
On Sun, Feb 25, 2018 at 08:44:46PM -0500, Jeff King wrote:
> On Sat, Feb 24, 2018 at 04:18:36PM +0100, Lars Schneider wrote:
>
> > > We always use the in-repo contents when generating 'diff'. I think
> > > by "attribute to be used in diff", what you are reallying after is
> > > to convert the in-
Stephen R Guglielmo writes:
> On Fri, Feb 23, 2018 at 5:45 PM, Junio C Hamano wrote:
>...
>> I am however starting to feel that
>> ...
>> may be a better approach.
> ...
> I'm happy to develop a new patch based on your recommendations. Should
> it be on top of the previous patch I sent or should
>From 9f7d43f29eaf6017b7b16261ce91d8ef182cf415 Mon Sep 17 00:00:00 2001
In-Reply-To: <20171218131249.gb4...@sigill.intra.peff.net>
References: <20171218131249.gb4...@sigill.intra.peff.net>
From: =?UTF-8?q?Torsten=20B=C3=B6gershausen?=
Date: Fri, 23 Feb 2018 20:53:34 +0100
Subject: [PATCH 0/1] Auto
From: Torsten Bögershausen
When an UTF-16 file is commited and later changed, `git diff` shows
"Binary files XX and YY differ".
When the user wants a diff in UTF-8, a textconv needs to be specified
in .gitattributes and the textconv must be configured.
A more user-friendly diff can be produced
On 2/26/2018 11:25 AM, SZEDER Gábor wrote:
Teach git the 'commit-graph' builtin that will be used for writing and
reading packed graph files. The current implementation is mostly
empty, except for an '--object-dir' option.
Since 'git commit-graph' is a builtin command, it shouldn't show up in
co
> Teach git the 'commit-graph' builtin that will be used for writing and
> reading packed graph files. The current implementation is mostly
> empty, except for an '--object-dir' option.
Since 'git commit-graph' is a builtin command, it shouldn't show up in
completion when doing 'git co'.
Please sq
On Mon, Feb 19, 2018 at 7:53 PM, Derrick Stolee wrote:
> +static int if_packed_commit_add_to_list(const struct object_id *oid,
> + struct packed_git *pack,
> + uint32_t pos,
> + void
During abbreviation checks, we navigate to the position within a
pack-index that an OID would be inserted and check surrounding OIDs
for the maximum matching prefix. This position may be beyond the
last position, because the given OID is lexicographically larger
than every OID in the pack. Then nth
On Fri, Feb 23, 2018 at 5:45 PM, Junio C Hamano wrote:
> 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-
On Mon, Feb 26, 2018 at 3:06 PM, Derrick Stolee wrote:
>
> Christian: do you want to submit the patch, or should I put one together?
I'd rather have you put one together.
Thanks,
Christian.
On 2/24/2018 12:42 AM, René Scharfe wrote:
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)
{
str
On 2/26/2018 5:23 AM, Christian Couder wrote:
On Mon, Feb 26, 2018 at 10:53 AM, Jeff King wrote:
On Mon, Feb 26, 2018 at 10:04:22AM +0100, Christian Couder wrote:
==21455== Use of uninitialised value of size 8
==21455==at 0x2D2A73: get_hex_char_from_oid (sha1_name.c:492)
==21455==by 0
On Mon, Feb 26 2018, Duy Nguyen jotted:
> On Mon, Feb 26, 2018 at 3:35 AM, Ævar Arnfjörð Bjarmason
> wrote:
>> My recently landed wildmatch test series was in preperation for some
>> more major wildmatch changes.
>>
>> Here's another series that prepares for bigger changes in wildmatch,
>> it ad
On Mon, Feb 26 2018, Duy Nguyen jotted:
> On Mon, Feb 26, 2018 at 3:35 AM, Ævar Arnfjörð Bjarmason
> wrote:
>> Add the scaffolding necessary for precompiling wildmatch()
>> patterns.
>>
>> There is currently no point in doing this with the wildmatch()
>> function we have now, since it can't make
On Mon, Feb 26 2018, Duy Nguyen jotted:
> On Mon, Feb 26, 2018 at 3:35 AM, Ævar Arnfjörð Bjarmason
> wrote:
>> diff --git a/config.c b/config.c
>> index b0c20e6cb8..0f595de971 100644
>> --- a/config.c
>> +++ b/config.c
>> @@ -210,6 +210,7 @@ static int include_by_gitdir(const struct config_optio
This is an initial attempt to add a "format-patch" command
to git-p4, following on from the earlier discussion about
shelving.
It uses the "p4 describe" command to generate the diff content and
post-processes it enough to generate git-style patches. These
can be fed to tools such as patch, or "git
It takes a list of P4 changelists and generates a patch for
each one, using "p4 describe".
This is especially useful for applying shelved changelists
to your git-p4 tree; the existing "git p4" subcommands do
not handle these.
That's because they "p4 print" the contents of each file at
a given rev
On Mon, Feb 26, 2018 at 4:12 AM, brian m. carlson
wrote:
> diff --git a/sha1_file.c b/sha1_file.c
> index 7493bc7f11..c41fbe2f01 100644
> --- a/sha1_file.c
> +++ b/sha1_file.c
> @@ -1227,22 +1227,18 @@ int oid_object_info_extended(const struct object_id
> *oid, struct object_info *oi
> st
On Thu, 22 Feb 2018 03:05:35 +, 'Peter Backes' wrote:
...
> The bigger issue is usually to copy with those pesky leap seconds. It
> makes a difference whether one uses solar seconds ("posix" style; those
> are more commonly seen) or atomic seconds ("right" style) for the UNIX
> timestamp.
I
On Mon, Feb 26, 2018 at 4:11 AM, brian m. carlson
wrote:
> @@ -44,7 +44,7 @@ void resolve_undo_write(struct strbuf *sb, struct
> string_list *resolve_undo)
> for (i = 0; i < 3; i++) {
> if (!ui->mode[i])
> continue;
> -
On Mon, Feb 26, 2018 at 5:17 AM, Duy Nguyen wrote:
> On Thu, Feb 22, 2018 at 7:31 AM, Junio C Hamano wrote:
>> * nd/worktree-move (2018-02-12) 7 commits
>>
>> "git worktree" learned move and remove subcommands.
>>
>> Expecting a reroll.
>> cf. <20180124095357.19645-1-pclo...@gmail.com>
>
> I t
On Mon, Feb 26, 2018 at 4:11 AM, brian m. carlson
wrote:
> @@ -465,7 +465,7 @@ static void write_one(struct strbuf *buffer, struct
> cache_tree *it,
> #endif
>
> if (0 <= it->entry_count) {
> - strbuf_add(buffer, it->oid.hash, 20);
> + strbuf_add(buffer, it->o
On Mon, Feb 26, 2018 at 11:56:42AM +0100, Andreas Krey wrote:
> > The bigger issue is usually to copy with those pesky leap seconds. It
> > makes a difference whether one uses solar seconds ("posix" style; those
> > are more commonly seen) or atomic seconds ("right" style) for the UNIX
> > times
Greetings,
I am desperately in need of a foreigner with a foreign account. I have
a profitable business that wil be of a benefit to both of us. Permit
me to disclose the details of the business to you
Ahmed Zama
On Mon, Feb 26, 2018 at 3:35 AM, Ævar Arnfjörð Bjarmason
wrote:
> My recently landed wildmatch test series was in preperation for some
> more major wildmatch changes.
>
> Here's another series that prepares for bigger changes in wildmatch,
> it adds an interface to pre-compile the patterns. Right
On Mon, Feb 26, 2018 at 3:35 AM, Ævar Arnfjörð Bjarmason
wrote:
> diff --git a/config.c b/config.c
> index b0c20e6cb8..0f595de971 100644
> --- a/config.c
> +++ b/config.c
> @@ -210,6 +210,7 @@ static int include_by_gitdir(const struct config_options
> *opts,
> int ret = 0, prefix;
>
On 2018-02-24 23:28, Ævar Arnfjörð Bjarmason wrote:
> My Time::Local 1.2300 on perl 5.024001 currently interprets "69" here as
> 1969, but after this it'll be 2069.
on one hand, there is already
perl -e 'use Time::Local;
print scalar gmtime(Time::Local::timegm(0,0,0,1,0,68))'
Sun Jan 1 00:00:00
On Mon, Feb 26, 2018 at 3:35 AM, Ævar Arnfjörð Bjarmason
wrote:
> Add the scaffolding necessary for precompiling wildmatch()
> patterns.
>
> There is currently no point in doing this with the wildmatch()
> function we have now, since it can't make any use of precompiling the
> pattern.
>
> But add
1 - 100 of 112 matches
Mail list logo
