Torsten Bögershausen writes:
> On 2016-08-03 18.42, larsxschnei...@gmail.com wrote:
>> The filter is expected to respond with the result content in zero
>> or more pkt-line packets and a flush packet at the end. Finally, a
>> "result=success" packet is expected if everything went well.
>> ---
From: Jeff Hostetler
Collect extra per-file data for porcelain V2 format.
The output of `git status --porcelain` leaves out many
details about the current status that clients might like
to have. This can force them to be less efficient as they
may need to launch secondary commands (and try to m
From: Jeff Hostetler
Update status manpage to include information about
porcelain v2 format.
Signed-off-by: Jeff Hostetler
---
Documentation/git-status.txt | 126 +--
1 file changed, 122 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-statu
From: Jeff Hostetler
Rename the various wt_status_print*() routines to be
wt_longstatus_print*() to make it clear that these
routines are only concerned with the normal/long
status output and reduce developer confusion as other
status formats are added in the future.
Signed-off-by: Jeff Hostetle
From: Jeff Hostetler
Update --porcelain argument to take optional version parameter
to allow multiple porcelain formats to be supported in the future.
The token "v1" is the default value and indicates the traditional
porcelain format. (The token "1" is an alias for that.)
Signed-off-by: Jeff H
From: Jeff Hostetler
Print per-file information in porcelain v2 format.
Signed-off-by: Jeff Hostetler
---
wt-status.c | 285 +++-
1 file changed, 284 insertions(+), 1 deletion(-)
diff --git a/wt-status.c b/wt-status.c
index ca8023e..4b6a
From: Jeff Hostetler
Test porcelain v2 status format.
Signed-off-by: Jeff Hostetler
---
t/t7064-wtstatus-pv2.sh | 597
1 file changed, 597 insertions(+)
create mode 100755 t/t7064-wtstatus-pv2.sh
diff --git a/t/t7064-wtstatus-pv2.sh b/t/t7064-
From: Jeff Hostetler
Expand porcelain v2 output to include branch and tracking
branch information. This includes the commit id, the branch,
the upstream branch, and the ahead and behind counts.
Signed-off-by: Jeff Hostetler
---
builtin/commit.c | 5
wt-status.c | 90
From: Jeff Hostetler
This patch series adds porcelain V2 format to status.
This provides detailed information about file changes
and about the current branch.
The new output is accessed via:
git status --porcelain=v2 [--branch]
This v5 patch series addresses all comments received
today abou
From: Jeff Hostetler
Add lf_to_nul() function to test-lib-functions.
Signed-off-by: Jeff Hostetler
---
t/test-lib-functions.sh | 4
1 file changed, 4 insertions(+)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 4f7eadb..fdaeb3a 100644
--- a/t/test-lib-functions.sh
+
From: Jeff Hostetler
Refactor the API between builtin/commit.c and wt-status.[ch].
Hide the details of the various wt_*status_print() routines inside
wt-status.c behind a single (new) wt_status_print() routine.
Eliminate the switch statements from builtin/commit.c.
Allow details of new status fo
Johannes Schindelin writes:
> Hi Junio & René,
>
> On Thu, 4 Aug 2016, Junio C Hamano wrote:
>
>> Let's try it this way. How about this as a replacement?
>
> I like it (with the if (s2) test intead of if (s1), of course). But please
> record René as author, maybe mentioning myself with a "Diagno
> On 05 Aug 2016, at 23:19, Torsten Bögershausen wrote:
>
> On 2016-08-05 15.08, Lars Schneider wrote:
>
> []
>> Yeah it could do that. But then the filter cannot do things like
>> modifying the index after the fact... however, that might be considered
>> nasty by the Git community anyways... I
> On 05 Aug 2016, at 23:34, Torsten Bögershausen wrote:
>
> On 2016-08-03 18.42, larsxschnei...@gmail.com wrote:
>> The filter is expected to respond with the result content in zero
>> or more pkt-line packets and a flush packet at the end. Finally, a
>> "result=success" packet is expected if ev
Stefan Beller writes:
> The plan for other layouts might be
>
> git submodule update --reference-dir /var/cache/
That is not a plan for "other layouts", but a plan for "the other
layout that was mentioned as a possibility". As I said, both
layouts are equally plausible, and I do not know if
On Fri, Aug 5, 2016 at 2:43 PM, Stefan Beller wrote:
> cov-build --dir cov-int make
For this you need to download their analytic tool and put it in
your $PATH. Let me see if I need to update the tool so it
enables finding more potential issues.
So that was an initial hurdle.
--
To unsubscri
On Fri, Aug 5, 2016 at 2:14 PM, Jeff King wrote:
>
> Unfortunately it is hard for me to test a one-off, as running it locally
> is a complete pain. Stefan set it up long ago to pull "pu" and email out
> the results from their central servers, so I just scan those emails for
> things that look lik
Stefan Beller writes:
> When giving a --reference while also giving --recurse, the alternates
> for the submodules are assumed to be in the superproject as well.
>
> In case they are not, we error out when cloning the submodule.
> However the update command succeeds as usual (with no alternates).
On 2016-08-03 18.42, larsxschnei...@gmail.com wrote:
> The filter is expected to respond with the result content in zero
> or more pkt-line packets and a flush packet at the end. Finally, a
> "result=success" packet is expected if everything went well.
>
> packet:
On Fri, Aug 5, 2016 at 2:31 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> I thought about rolling it as a strict bugfix; but the bug is shaded by the
>> inverse bug in the helper, so the user would never see an issue.
>
> Ahh, OK, because the helper accepts "--reference" "--reference=foo
Stefan Beller writes:
> I thought about rolling it as a strict bugfix; but the bug is shaded by the
> inverse bug in the helper, so the user would never see an issue.
Ahh, OK, because the helper accepts "--reference" "--reference=foo"
as a OPT_STRING whose value happens to be "--reference=foo",
On 08/05/2016 05:02 PM, Jeff King wrote:
On Tue, Aug 02, 2016 at 10:12:14AM -0400, Jeff Hostetler wrote:
+static void wt_porcelain_v2_print_unmerged_entry(
+ struct string_list_item *it,
+ struct wt_status *s)
+{
+ struct wt_status_change_data *d = it->util;
+ const st
On 08/05/2016 04:55 PM, Ramsay Jones wrote:
Signed-off-by: Ramsay Jones
---
Hi Jeff,
If you need to re-roll your 'jh/status-v2-porcelain' branch, could
you please squash this into the relevant patch (37f7104f, "status:
print per-file porcelain v2 status data", 02-08-2016).
Thanks!
ATB,
Ra
On Fri, Aug 5, 2016 at 2:20 PM, Martin Fick wrote:
> On Friday, August 05, 2016 08:39:58 AM you wrote:
>> * A new topic, when you merge it to the "lit" branch, you
>> describe the cover as the merge commit message.
>>
>> * When you updated an existing topic, you tell a tool
>> like "rebase -i -p
On Fri, Aug 5, 2016 at 12:47 PM, Junio C Hamano wrote:
> * You want the "clone" command above with "--recursive" to do "the
>right thing". That is, the clone of the superproject borrows
>from /var/cache/super.git local mirror, and the clone of xyzzy
>that would be made at .git/module
On Fri, Aug 5, 2016 at 2:14 PM, Jeff King wrote:
>
> Unfortunately it is hard for me to test a one-off, as running it locally
> is a complete pain. Stefan set it up long ago to pull "pu" and email out
> the results from their central servers, so I just scan those emails for
> things that look like
On Friday, August 05, 2016 08:39:58 AM you wrote:
> * A new topic, when you merge it to the "lit" branch, you
> describe the cover as the merge commit message.
>
> * When you updated an existing topic, you tell a tool
> like "rebase -i -p" to recreate "lit" branch on top of
> the mainline. This
On 2016-08-05 15.08, Lars Schneider wrote:
[]
> Yeah it could do that. But then the filter cannot do things like
> modifying the index after the fact... however, that might be considered
> nasty by the Git community anyways... I am thinking about dropping
> this patch in the next roll as it is not
On Fri, Aug 5, 2016 at 2:06 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>>> - ${reference:+--reference "$reference"} \
>>> + ${reference:+"$reference"} \
>>
>> Note how this changed the API of the submodule--helper.
>> Currently we pass in --reference $referenc
Stefan Beller writes:
> Signed-off-by: Stefan Beller
> ---
That's a bit sketchy description. From the title, I expected that
we would see one additional 'unsigned super_reference : 1;' field in
some structure, but that is not what is happening. The log message
needs to describe what these str
On Fri, Aug 05, 2016 at 02:09:48PM -0700, Junio C Hamano wrote:
> On Fri, Aug 5, 2016 at 2:02 PM, Jeff King wrote:
> > On Tue, Aug 02, 2016 at 10:12:14AM -0400, Jeff Hostetler wrote:
> >> + switch (d->stagemask) {
> >> + case 1: key = "DD"; break; /* both deleted */
> >> + ...
> >> +
On Fri, Aug 5, 2016 at 2:02 PM, Jeff King wrote:
> On Tue, Aug 02, 2016 at 10:12:14AM -0400, Jeff Hostetler wrote:
>> + switch (d->stagemask) {
>> + case 1: key = "DD"; break; /* both deleted */
>> + ...
>> + case 7: key = "UU"; break; /* both modified */
>> + }
>> [...]
>> + f
Stefan Beller writes:
>> - ${reference:+--reference "$reference"} \
>> + ${reference:+"$reference"} \
>
> Note how this changed the API of the submodule--helper.
> Currently we pass in --reference $reference
> and $reference consists of the string "--reference" and the
On Tue, Aug 02, 2016 at 10:12:14AM -0400, Jeff Hostetler wrote:
> +static void wt_porcelain_v2_print_unmerged_entry(
> + struct string_list_item *it,
> + struct wt_status *s)
> +{
> + struct wt_status_change_data *d = it->util;
> + const struct cache_entry *ce;
> + struct strbu
Stefan Beller wrote:
> On Fri, Aug 5, 2016 at 1:20 AM, Johannes Schindelin
> wrote:
> > Yet another option would be to have a tool that integrates with the Git
> > repository of the Git mailing list represented by public-inbox.
>
> So my first reaction to that would be: you could push you patche
Call string_list_split() for cutting a space separated list into pieces
instead of reimplementing it based on struct strategy. The attr member
of struct strategy was not used split_merge_strategies(); it was a pure
string operation. Also be nice and clean up once we're done splitting;
the old cod
Signed-off-by: Ramsay Jones
---
Hi Michael,
If you need to re-roll your 'mh/diff-indent-heuristic' branch, could
you please squash this into the relevant patch (e199b6e2, "diff: improve
positioning of add/delete blocks in diffs", 04-08-2016).
Thanks!
ATB,
Ramsay Jones
xdiff/xdiffi.c | 4 ++-
Signed-off-by: Ramsay Jones
---
Hi Jeff,
If you need to re-roll your 'jh/status-v2-porcelain' branch, could
you please squash this into the relevant patch (37f7104f, "status:
print per-file porcelain v2 status data", 02-08-2016).
Thanks!
ATB,
Ramsay Jones
wt-status.c | 2 +-
1 file changed,
Stefan Beller writes:
> Allow users to pass in multiple references, just as clone accepts multiple
> references as well.
As these are passed-thru to the underlying "git clone", this change
makes perfect sense to me.
Will queue.
--
To unsubscribe from this list: send the line "unsubscribe git"
Stefan Beller writes:
> Tests consisting of one line each can be consolidated to have fewer tests
> to run as well as fewer lines of code.
>
> When having just a few git commands, do not create a new shell but
> use the -C flag in Git to execute in the correct directory.
Good motivations.
> Sig
Initialize a string_list right when it's defined. That's shorter, saves
a function call and makes it more obvious that we're using the NODUP
variant here.
Signed-off-by: Rene Scharfe
---
merge-recursive.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/merge-recursive.c b/
Initialize struct child_process variables already when they're defined.
That's shorter and saves a function call.
Signed-off-by: Rene Scharfe
---
builtin/submodule--helper.c | 3 +--
builtin/worktree.c | 6 ++
2 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/builtin/su
Call strbuf_addstr() for adding a simple string to a strbuf instead of
using the heavier strbuf_addf(). This is shorter and documents the
intent more clearly.
Signed-off-by: Rene Scharfe
---
builtin/fmt-merge-msg.c | 2 +-
http.c | 2 +-
sequencer.c | 2 +-
3 files
Stefan Beller writes:
> No functional change intended. This commit only changes formatting
> to the style we recently use, e.g. starting the body of a test with a
> single quote on the same line as the header, and then having the test
> indented in the following lines.
>
> Whenever we change dire
On Fri, Aug 05, 2016 at 06:19:57PM +, Eric Wong wrote:
> Jeff King wrote:
> > On Fri, Aug 05, 2016 at 05:28:05AM -0400, Jeff King wrote:
> > > I do find it visually a little harder to navigate through threads,
> > > because there's not much styling there, and the messages seem to run
> > > in
On Fri, Aug 05, 2016 at 05:04:27PM +0200, Duy Nguyen wrote:
> On Fri, Aug 5, 2016 at 11:28 AM, Jeff King wrote:
> > There was discussion a long time ago about storing a common zlib
> > dictionary in the packfile and using it for all of the objects. I don't
> > recall whether there were any patche
Stefan Beller writes:
> Currently when cloning a superproject with --recursive and --reference
> only the superproject learns about its alternates. The submodules are
> cloned independently, which may incur lots of network costs.
>
> Assume that the reference repository has the submodules a
On Mon, Sep 17, 2001 at 10:00:00AM +, Stefan Beller wrote:
> But both send-email as well as mail-patch-series as well as git-series
> are all about the *sending* part. Not about the back and forth part, i.e.
> these don't deal with: "here is a fixup on top". And by that I mean
> receiving mails
Debian Testing with v4.5.5-1 kernel, git v2.8.1.
I seem to have a broken git setup somehow on this machine - I'm
currently testing the ability to fetch PRs from Github following [0],
e.g. testing with a PR on dattobd[1]:
git clone https://github.c
> - ${reference:+--reference "$reference"} \
> + ${reference:+"$reference"} \
Note how this changed the API of the submodule--helper.
Currently we pass in --reference $reference
and $reference consists of the string "--reference" and the actual
reference. So it looked l
Lars Schneider wrote:
> > On 27 Jul 2016, at 11:41, Eric Wong wrote:
> > larsxschnei...@gmail.com wrote:
> >> +static int apply_protocol_filter(const char *path, const char *src,
> >> size_t len,
> >> + int fd, struct strbuf *dst,
> >> const char *cmd,
>
Johannes Schindelin wrote:
> On Thu, 4 Aug 2016, Stefan Beller wrote:
> > git send-email/format-patch recently learned to include a base commit
>
> You may have noticed that my mail-patch-series.sh-generated code
> submissions contain that base commit. But they still do not contain the
> SHA-1s o
From: "Duy Nguyen"
On Wed, Aug 3, 2016 at 6:07 PM, Johannes Schindelin
wrote:
It would be a totally different matter, of course, if you used the
branches I publish via my GitHub repository, added fixup! and squash!
commits, published the result to a public repository and then told me to
pull f
Christian Couder writes:
> On Thu, Aug 4, 2016 at 11:28 PM, Junio C Hamano wrote:
>> Jeff King writes:
>>
>>> I wondered if that would then let us drop set_warn_routine(), but it
>>> looks like there are other warning() calls it cares about. So that would
>>> invalidate the last paragraph here,
On 08/05/2016 02:12 PM, Junio C Hamano wrote:
Jeff Hostetler writes:
+##
+## Confirm output prior to initial commit.
+##
+
+test_expect_success pre_initial_commit_0
On 08/05/2016 01:50 PM, Junio C Hamano wrote:
Jeff Hostetler writes:
+Porcelain Format Version 2
+~~
+
+Version 2 format adds more detailed information about the state of
+the worktree and changed items. Version 2 also defines an extensible
+set of easy to parse opti
Jeff King wrote:
> On Fri, Aug 05, 2016 at 05:28:05AM -0400, Jeff King wrote:
> > I do find it visually a little harder to navigate through threads,
> > because there's not much styling there, and the messages seem to run
> > into one another. I don't know if a border around the divs or something
On 08/05/2016 01:01 PM, Junio C Hamano wrote:
Jeff Hostetler writes:
/*
+ * Print branch information for porcelain v2 output. These lines
+ * are printed when the '--branch' parameter is given.
+ *
+ *# branch.oid
+ *# branch.head
Just bikeshedding, but ...
+ if (!s->b
Jeff Hostetler writes:
> +##
> +## Confirm output prior to initial commit.
> +##
> +
> +test_expect_success pre_initial_commit_0 '
Bikeshedding, but our codebase seems
Hi Johannes,
On Fri, Aug 5, 2016 at 1:20 AM, Johannes Schindelin
wrote:
> Hi Stefan,
>
> On Thu, 4 Aug 2016, Stefan Beller wrote:
>
>> On Thu, Aug 4, 2016 at 8:58 AM, Johannes Schindelin
>> wrote:
>> >
>> >> If we were to change our workflows drastically, I'd propose to go a
>> >> way[1] similar
Jeff Hostetler writes:
> +Porcelain Format Version 2
> +~~
> +
> +Version 2 format adds more detailed information about the state of
> +the worktree and changed items. Version 2 also defines an extensible
> +set of easy to parse optional headers.
> +
> +Header lines start
On Fri, Aug 5, 2016 at 10:31 AM, Lars Schneider
wrote:
>
>> On 04 Aug 2016, at 18:14, Junio C Hamano wrote:
>>
>> signature would look more like write(2) and deserve to be called
>> packet_write() but unfortunately the name is taken by what should
>> have called packet_fmt() or something, but tha
> On 04 Aug 2016, at 18:14, Junio C Hamano wrote:
>
> Jeff King writes:
>
>> The cost of write() may vary on other platforms, but the cost of memcpy
>> generally shouldn't. So I'm inclined to say that it is not really worth
>> micro-optimizing the interface.
>>
>> I think the other issue is t
Jeff Hostetler writes:
> /*
> + * Print branch information for porcelain v2 output. These lines
> + * are printed when the '--branch' parameter is given.
> + *
> + *# branch.oid
> + *# branch.head
Just bikeshedding, but ...
> + if (!s->branch)
> + fprintf(s->fp, "# b
Lars Schneider writes:
> However, besides the bogus performance argument I introduced that function
> to allow packet writs to fail using the `gentle` parameter:
> http://public-inbox.org/git/D116610C-F33A-43DA-A49D-0B33958822E5%40gmail.com/
>
> Would you be OK if I introduce packet_write_gently(
Johannes Schindelin writes:
> Please note that t7001 *specifically* tests for the opposite of what you
> want, then ;-)
Yes, I know. I am torn.
It seems "mv A B/" (not "git mv") when B does not exist does the
same "wrong" thing, so the existing behaviour is at least consistent
with the command
Johannes Schindelin writes:
> This setup will from now on test next & pu in the Git for Windows SDK, and
> rebase Git for Windows' current master to git.git's maint, master, next &
> pu, every morning after a weekday (unless I forget to turn on my laptop,
> that is).
Sounds really good. Thanks.
Hi Peff,
On Wed, 3 Aug 2016, Jeff King wrote:
> On Wed, Aug 03, 2016 at 09:08:48AM -0700, Junio C Hamano wrote:
>
> > > However, I could imagine that we actually want this to be more
> > > extensible. After all, all you are doing is to introduce a new
> > > rebase -i command that does nothing e
Hi Junio,
On Fri, 5 Aug 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > When calling `rename("dir", "non-existing-dir/")` on Linux, it silently
> > succeeds, stripping the trailing slash of the second argument.
> >
> > This is all good and dandy but this behavior disagrees with
Johannes Schindelin writes:
> When calling `rename("dir", "non-existing-dir/")` on Linux, it silently
> succeeds, stripping the trailing slash of the second argument.
>
> This is all good and dandy but this behavior disagrees with the specs at
>
> http://pubs.opengroup.org/onlinepubs/9699919799/f
Hi Junio,
On Thu, 4 Aug 2016, Junio C Hamano wrote:
> Jeff King writes:
>
> > Like you, I have occasionally been bitten by Junio doing a fixup, and
> > then I end up re-rolling, and lose that fixup.
>
> ... which usually is caught when I receive the reroll, as I try to apply
> to the same base
"Michael S. Tsirkin" writes:
> On Thu, Sep 10, 2015 at 11:39:49AM -0700, Junio C Hamano wrote:
>> The problem with "empty commit trick" is that it is a commit whose
>> sole purpose is to describe the series, and its presence makes it
>> clear where the series ends, but the topology does not tell
Hi Junio,
On Thu, 4 Aug 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > Ever since 66a155b (Enable output buffering in merge-recursive.,
> > 2007-01-14), we had a problem: When the merge failed in a fatal way, all
> > regular output was swallowed because we called die() and did
Hi Junio,
On Thu, 4 Aug 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > With GCC 6, the strdup() function is declared with the "nonnull"
> > attribute, stating that it is not allowed to pass a NULL value as
> > parameter.
> >
> > In nedmalloc()'s reimplementation of strdup(), Po
Hi Junio & René,
On Thu, 4 Aug 2016, Junio C Hamano wrote:
> Let's try it this way. How about this as a replacement?
I like it (with the if (s2) test intead of if (s1), of course). But please
record René as author, maybe mentioning myself with a "Diagnosed-by:"
line.
FWIW today's `pu` does pas
Hi Richard,
On Fri, 5 Aug 2016, Richard Ipsum wrote:
> On Thu, Aug 04, 2016 at 09:42:18AM -0700, Stefan Beller wrote:
> > On Thu, Aug 4, 2016 at 8:58 AM, Johannes Schindelin
> > wrote:
> > >
> > >> If we were to change our workflows drastically, I'd propose to go a
> > >> way[1] similar to noted
Hi Duy,
On Fri, 5 Aug 2016, Duy Nguyen wrote:
> On the topic of fixup and squash and everything. Is anyone else
> annoyed that the commit title is taken for fixup!, squash!
> instructions?
I do not know about others, but I am not annoyed by those commit titles. I
think they make tons of sense.
On Fri, Aug 5, 2016 at 11:28 AM, Jeff King wrote:
> There was discussion a long time ago about storing a common zlib
> dictionary in the packfile and using it for all of the objects. I don't
> recall whether there were any patches, though. It does create some
> complications with serving clones/fe
On Wed, Aug 3, 2016 at 6:07 PM, Johannes Schindelin
wrote:
> It would be a totally different matter, of course, if you used the
> branches I publish via my GitHub repository, added fixup! and squash!
> commits, published the result to a public repository and then told me to
> pull from there, that
> On 04 Aug 2016, at 18:14, Junio C Hamano wrote:
>
> Jeff King writes:
>
>> The cost of write() may vary on other platforms, but the cost of memcpy
>> generally shouldn't. So I'm inclined to say that it is not really worth
>> micro-optimizing the interface.
>>
>> I think the other issue is t
When calling `rename("dir", "non-existing-dir/")` on Linux, it silently
succeeds, stripping the trailing slash of the second argument.
This is all good and dandy but this behavior disagrees with the specs at
http://pubs.opengroup.org/onlinepubs/9699919799/functions/rename.html
that state clearly
Hi Junio,
On Thu, 4 Aug 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > The newly-added test case wants to commit a file "c.t" (note the lower
> > case) when a previous test case already committed a file "C.t". This
> > confuses Git to the point that it thinks "c.t" was not stag
Am 04.08.2016 um 12:45 nachm. schrieb Junio C Hamano :
> Andrew Keller writes:
>
>> In summary, I think I prefer #2 from a usability point of view, however I’m
>> having
>> trouble proving that #1 is actually *bad* and should be disallowed.
>
> Yeah, I agree with your argument from the usabili
> On 04 Aug 2016, at 12:18, Jakub Narębski wrote:
>
> ...
+
+ sigchain_push(SIGPIPE, SIG_IGN);
>>>
>>> Hmmm... ignoring SIGPIPE was good for one-shot filters. Is it still
>>> O.K. for per-command persistent ones?
>>
>> Very good question. You are right... we don't want to ignore an
> On 04 Aug 2016, at 01:15, Jeff King wrote:
>
> On Thu, Aug 04, 2016 at 01:09:57AM +0200, Lars Schneider wrote:
>
>>> Or better yet, do not require a shutdown at all. The filter sees EOF and
>>> knows there is nothing more to do. If we are in the middle of an
>>> operation, then it knows git d
> On 04 Aug 2016, at 00:46, Jeff King wrote:
>
> On Wed, Aug 03, 2016 at 11:48:00PM +0200, Lars Schneider wrote:
>
>> OK. Is this the v2 discussion you are referring to?
>> http://public-inbox.org/git/1461972887-22100-1-git-send-email-sbeller%40google.com/
>>
>> What format do you suggest?
>>
> On 03 Aug 2016, at 22:12, Jakub Narębski wrote:
>
> [This response might have been invalidated by v4]
>
> W dniu 01.08.2016 o 14:00, Lars Schneider pisze:
>>> On 30 Jul 2016, at 12:49, Jakub Narębski wrote:
>>> W dniu 30.07.2016 o 01:37, larsxschnei...@gmail.com pisze:
Sometimes p
On Thu, Aug 04, 2016 at 09:42:18AM -0700, Stefan Beller wrote:
> On Thu, Aug 4, 2016 at 8:58 AM, Johannes Schindelin
> wrote:
> >
> >> If we were to change our workflows drastically, I'd propose to
> >> go a way[1] similar to notedb in Gerrit, or git-series,
> >
> > Gerrit is a huge, non-distribut
> On 03 Aug 2016, at 22:05, Jakub Narębski wrote:
>
> [This response might have been invalidated by v4]
>
> W dniu 01.08.2016 o 13:33, Lars Schneider pisze:
>>> On 30 Jul 2016, at 12:30, Jakub Narębski wrote:
>
#define hex(a) (hexchar[(a) & 15])
>>>
>>> I guess that this is inherited f
> On 03 Aug 2016, at 20:30, Jakub Narębski wrote:
>
> The ultimate goal is to be able to run filter drivers faster for both `clean`
> and `smudge` operations. This is done by starting filter driver once per
> git command invocation, instead of once per file being processed. Git needs
> to pass
> On 02 Aug 2016, at 21:56, Torsten Bögershausen wrote:
>
> On Sun, Jul 31, 2016 at 11:45:08PM +0200, Lars Schneider wrote:
>>
>>> On 31 Jul 2016, at 22:36, Torstem Bögershausen wrote:
>>>
>>>
>>>
Am 29.07.2016 um 20:37 schrieb larsxschnei...@gmail.com:
From: Lars Schneider
Jeff King wrote:
> On Fri, Aug 05, 2016 at 05:28:05AM -0400, Jeff King wrote:
>
> > On Sun, Jul 10, 2016 at 12:48:13AM +, Eric Wong wrote:
> >
> > > Very much a work-in-progress, but NNTP and HTTP/HTTPS sorta work
> > > based on stuff that is on gmane and stuff I'm accumulating by
> > > bein
On Fri, Aug 05, 2016 at 05:28:05AM -0400, Jeff King wrote:
> On Sun, Jul 10, 2016 at 12:48:13AM +, Eric Wong wrote:
>
> > Very much a work-in-progress, but NNTP and HTTP/HTTPS sorta work
> > based on stuff that is on gmane and stuff I'm accumulating by
> > being a subscriber.
>
> I checked t
On Sun, Jul 10, 2016 at 12:48:13AM +, Eric Wong wrote:
> Very much a work-in-progress, but NNTP and HTTP/HTTPS sorta work
> based on stuff that is on gmane and stuff I'm accumulating by
> being a subscriber.
I checked this out when you posted it, and have been using it the past
few weeks. I r
Jeff King wrote:
> On Fri, Aug 05, 2016 at 08:26:30AM +, Eric Wong wrote:
>
> > > I'm not sure which mallocs you mean. I allocate one struct per node,
> > > which seems like a requirement for a linked list. If you mean holding an
> > > extra list struct around an existing pointer (rather than
Johannes Schindelin wrote:
Agreed on all above points :>
> On Thu, 4 Aug 2016, Eric Wong wrote:
> > Of course, centralized systems are unacceptable to me;
> > and with that I'll never claim any network service I run
> > will be reliable :)
>
> Hehehe. I guess that's why the public-inbox is back
On Fri, Aug 05, 2016 at 08:26:30AM +, Eric Wong wrote:
> > I'm not sure which mallocs you mean. I allocate one struct per node,
> > which seems like a requirement for a linked list. If you mean holding an
> > extra list struct around an existing pointer (rather than shoving the
> > prev/next p
Jeff King wrote:
> On Fri, Aug 05, 2016 at 08:02:31AM +, Eric Wong wrote:
>
> > > I just introduced another doubly-linked list in [1]. It adds some MRU
> > > features on top of the list, but it could in theory be built on top of a
> > > generic doubly-linked list.
> >
> > Yes, and you'd be a
Hi Eric,
On Thu, 4 Aug 2016, Eric Wong wrote:
> Stefan Beller wrote:
> > On Thu, Aug 4, 2016 at 8:58 AM, Johannes Schindelin
> > wrote:
> > > I guess I have no really good idea yet, either, how to retain the ease of
> > > access of sending mails to the list, yet somehow keep a strong tie with
>
Hi Stefan,
On Thu, 4 Aug 2016, Stefan Beller wrote:
> On Thu, Aug 4, 2016 at 8:58 AM, Johannes Schindelin
> wrote:
> >
> >> If we were to change our workflows drastically, I'd propose to go a
> >> way[1] similar to notedb in Gerrit, or git-series,
> >
> > Gerrit is a huge, non-distributed system
1 - 100 of 109 matches
Mail list logo
