On Wed, Apr 13, 2016 at 8:55 AM, Nguyễn Thái Ngọc Duy wrote:
> Signed-off-by: Nguyễn Thái Ngọc Duy
> ---
> diff --git a/t/t5500-fetch-pack.sh b/t/t5500-fetch-pack.sh
> @@ -661,4 +661,26 @@ test_expect_success 'fetch shallow since ...' '
> +test_expect_success 'fetch exclude tag one' '
> + g
On Wed, Apr 13, 2016 at 8:55 AM, Nguyễn Thái Ngọc Duy wrote:
> Signed-off-by: Nguyễn Thái Ngọc Duy
> ---
> diff --git a/builtin/clone.c b/builtin/clone.c
> @@ -44,6 +44,7 @@ static int deepen;
> +static struct string_list option_not = STRING_LIST_INIT_NODUP;
> @@ -52,6 +53,13 @@ static struct str
On Wed, Apr 13, 2016 at 8:55 AM, Nguyễn Thái Ngọc Duy wrote:
> Signed-off-by: Nguyễn Thái Ngọc Duy
> ---
> diff --git a/builtin/fetch.c b/builtin/fetch.c
> @@ -41,6 +41,7 @@ static int max_children = 1;
> +static struct string_list deepen_not = STRING_LIST_INIT_NODUP;
> @@ -50,6 +51,13 @@ static
Combined with "git format-patch --pretty=mboxrd", this should
allow us to round-trip commit messages with embedded mbox
"From " lines without corruption.
Signed-off-by: Eric Wong
---
Documentation/git-am.txt | 3 ++-
builtin/am.c | 14 +++---
t/t4150-am.sh| 20 ++
This will allow us to parse the output of --pretty=mboxrd
and the output of other mboxrd generators.
Signed-off-by: Eric Wong
---
Documentation/git-mailsplit.txt | 7 ++-
builtin/mailsplit.c | 18 ++
t/t5100-mailinfo.sh | 31 ++
This output format prevents format-patch output from breaking
readers if somebody copy+pasted an mbox into a commit message.
Unlike the traditional "mboxo" format, "mboxrd" is designed to
be fully-reversible. "mboxrd" also gracefully degrades to
showing extra ">" in existing "mboxo" readers.
Thi
Changes since v2:
* beef up tests, including accounting for the trailing whitespace
omission in pretty output but still accepting and preserving
trailing whitespace in mailsplit.
* indicate disabling variable interpolation in heredoc (but
using variable interpolation as needed for trailing
On Wed, Apr 13, 2016 at 8:55 AM, Nguyễn Thái Ngọc Duy wrote:
> Signed-off-by: Nguyễn Thái Ngọc Duy
> ---
> diff --git a/t/t5539-fetch-http-shallow.sh b/t/t5539-fetch-http-shallow.sh
> @@ -73,5 +73,31 @@ test_expect_success 'no shallow lines after receiving ACK
> ready' '
> )
> '
>
> +te
On Sun, Jun 5, 2016 at 12:54 AM, Thomas Braun
wrote:
> Hi,
>
> the following procedure
>
> mkdir test
> cd test
> git init
> echo 1 >file
> git add --intent-to-add file
> git commit -m "blurb"
>
> results in a commit. I would have expected that git commit complains,
> as I have not pased the --all
On Sat, Jun 4, 2016 at 11:30 PM, Junio C Hamano wrote:
>> The patch does not do fancy stuff like this yet, but it can because
>> lines exceeding terminal width is already excluded from column width
>> calculation. So far the output looks good on my terminal (192 chars,
>> can't overflow or refname
We do align "remote -> local" output by allocating 10 columns to
"remote". That produces aligned output only for short refs. An extra
pass is performed to find the longest remote ref name (that does not
produce a line longer than terminal width) to produce better aligned
output.
Signed-off-by: Ngu
In the "remote -> local" line, if either ref is a substring of the
other, the common part in the other string is replaced with "$". For
example
abc-> origin/abc
refs/pull/123/head -> pull/123
become
abc -> origin/$
refs/$/head -> pull/123
Activated with f
Most of the time, ref update lines are
variable-long-name -> fixed-remote/variable-long-name
With fetch.output set to "compact" such a line will be shown as
{ -> fixed-remote}/variable-long-name
This keeps the output aligned (because the variable part is always at
the end) and reduce du
This documents the ref update status of fetch. The structure of this
output is defined in [1]. The ouput content is refined a bit in [2]
[3] [4].
This patch is a copy from git-push.txt, modified a bit because the
flag '-' means different things in push (delete) and fetch (tag
update).
PS. For cod
This makes the fetch flag code consistent with push, where '-' means
deleted ref.
Signed-off-by: Nguyễn Thái Ngọc Duy
---
Documentation/git-fetch.txt | 4 ++--
builtin/fetch.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-fetch.txt b/Docum
This is so people can play with new output format... v3 adds one extra
pass to calculate width (4/6) and swap flag code 'x' and '-' with '-'
and 't' to align with push flag code (3/6). These are definitely good
improvements.
5/6 and 6/6 add two new formats "{ -> origin}/abc" and "abc -> origin/$".
This makes it easier to change the formatting later. And it makes sure
translators cannot mess up format specifiers and break Git.
There are a couple call sites where the length of the second column is
TRANSPORT_SUMMARY_WIDTH instead of calculated by TRANSPORT_SUMMARY(),
which is enforced now. The
hey git
http://anilambulanceservicesdelhi.com/whatever.php?largest=1evvn57g1pz1vu
bolaji jibodu
--
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
On Sat, Jun 04, 2016 at 04:51:28PM +0200, Torsten Bögershausen wrote:
> On 2016-06-04 07.14, Mike Hommey wrote:
> > On Fri, Jun 03, 2016 at 04:47:33PM -0700, Junio C Hamano wrote:
> >> Mike Hommey writes:
> >>
> >>> In fact, the parser doesn't even reject the one that is considered
> >>> invalid (
Hi,
the following procedure
mkdir test
cd test
git init
echo 1 >file
git add --intent-to-add file
git commit -m "blurb"
results in a commit. I would have expected that git commit complains,
as I have not pased the --allow-empty option.
Is that intended behaviour?
Tested with 2.8.3.windows.1 an
Duy Nguyen writes:
>> Peff suggested that a two-pass approach might not be too bad, but had
>> problems when he tried it with extra-long refs. Maybe those problems
>> could be dealt with, and we could get a simple, aligned output?
>
> The good thing about 2/3 is we can customize the output eas
Mike Hommey writes:
> From my POV, the desired outcome from this patch series is that there is
> no change of behavior, and Torsten's fix makes
> git://[example.com:123]:/path/to/repo urls handled the same before and
> after the patch series.
OK.
I somehow suspect nobody cares too much about wh
Currently, a user wanting to prevent accidental pushes to the wrong
remote has to create a pre-push hook. The feature offers a
configuration to allow users to prevent accidental pushes to the wrong
remote. The user may define a list of whitelisted remotes, a list of
blacklisted remotes and a defau
On 2016-06-04 07.14, Mike Hommey wrote:
> On Fri, Jun 03, 2016 at 04:47:33PM -0700, Junio C Hamano wrote:
>> Mike Hommey writes:
>>
>>> In fact, the parser doesn't even reject the one that is considered
>>> invalid (the first).
>>
>> My question was what the desired behaviour is, and if your "fix"
When -S or -G is used as a filter option, the resulting commit list
rarely contains all matching commits. Only a certain number of commits
are displayed and the rest are missing.
"git log --boundary -S" does not return as many boundary commits as you
might expect. gitk makes up for this in closeva
25 matches
Mail list logo
