Signed-off-by: Elijah Newren
---
Documentation/git-fast-export.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-fast-export.txt
b/Documentation/git-fast-export.txt
index ce954be532..fda55b3284 100644
--- a/Documentation/git-fast-export.txt
+++ b
Signed-off-by: Elijah Newren
---
Documentation/git-fast-import.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-fast-import.txt
b/Documentation/git-fast-import.txt
index e81117d27f..7ab97745a6 100644
--- a/Documentation/git-fast-import.txt
+++ b
Konstantin Ryabitsev writes:
> On Thu, Nov 15, 2018 at 07:54:32PM +0100, Ævar Arnfjörð Bjarmason wrote:
>> > I think that if we use the "principle of least surprise," insteadOf
>> > rules shouldn't be applied for git-request-pull URLs.
>>
>> I hav
the possible values for
submodule..ignore ("all") don't make sense unless comparing with
the working tree. This is also how show/log -p behaved in git <2.15.
So I think that clarifying that it is about modifications *to the
working tree* would be a good idea.
>> I'm also starting to
On Thu, Nov 15, 2018 at 1:33 PM Michael Forney wrote:
>
> On 2018-11-15, Stefan Beller wrote:
> > On Wed, Nov 14, 2018 at 10:05 PM Michael Forney
> > wrote:
> >> Looking at ff6f1f564c, I don't really see anything that might be
> >> related to git-add, git
-lib.c| 15 +--
diff.c| 22 ++
3 files changed, 11 insertions(+), 27 deletions(-)
diff --git a/builtin/add.c b/builtin/add.c
index f65c17229..9902f7742 100644
--- a/builtin/add.c
+++ b/builtin/add.c
@@ -117,7 +117,6 @@ int add_files_to_cache(const char *
On 2018-11-15, Stefan Beller wrote:
> On Wed, Nov 14, 2018 at 10:05 PM Michael Forney
> wrote:
>> Looking at ff6f1f564c, I don't really see anything that might be
>> related to git-add, git-reset, or git-diff, so I'm guessing that this
>> only worked before because the
gt;>
> >> Maybe looking through the series 614ea03a71
> >> (Merge branch 'bw/submodule-config-cleanup', 2017-08-26)
> >> to understand why it happened in the context would be a good start.
> >
> > Thanks, that's a good idea. I'll take a look through tha
> I have a git repository which contains a number of submodules that
> refer to external repositories. Some of these repositories need to
> patched in some way, so patches are stored alongside the submodules,
> and are applied when building. This mostly works fine, but causes
> sub
On Thu, Nov 15, 2018 at 07:54:32PM +0100, Ævar Arnfjörð Bjarmason wrote:
> > I think that if we use the "principle of least surprise," insteadOf
> > rules shouldn't be applied for git-request-pull URLs.
>
> I haven't used request-pull so I don't have much of an opinion
On Thu, Nov 15 2018, Konstantin Ryabitsev wrote:
> Hi, all:
>
> Looks like setting url.insteadOf rules alters the output of
> git-request-pull. I'm not sure that's the intended use of insteadOf,
> which is supposed to replace URLs for local use, not to expose them
> publicly (
Hi, all:
Looks like setting url.insteadOf rules alters the output of
git-request-pull. I'm not sure that's the intended use of insteadOf,
which is supposed to replace URLs for local use, not to expose them
publicly (but I may be wrong). E.g.:
$ git request-pull HEAD^ git://foo.example.com
cted is
> > > now REBASE-i.
> >
> > We should be able to make that test pass, still, by writing out a special
> > file (e.g. $state_dir/opt_m) and testing for that. Users are oddly upset
> > when their expectations are broken... (and I actually agree with th
odule-config-cleanup', 2017-08-26)
>> to understand why it happened in the context would be a good start.
>
> Thanks, that's a good idea. I'll take a look through that series.
Interesting. If I build git from master after reverting 55568086, I do
indeed observe the issue it claims to fix (una
ules. I finally got around to bisecting this to commit
>> > 5556808690ea245708fb80383be5c1afee2fb3eb (add, reset: ensure
>> > submodules can be added or reset).
>
> Uh. :(
>
> See the discussion starting at
> https://public-inbox.org/git/20170725213928
Hi Phillip,
On Mon, Nov 12, 2018 at 10:21 AM Phillip Wood wrote:
> >> -Flags only understood by the am backend:
> >> +The following options:
> >>
> >> * --committer-date-is-author-date
> >> * --ignore-date
> >> @@ -520,15 +512,12 @@ Flags only understood by the am backend:
> >> *
ake that test pass, still, by writing out a special
> file (e.g. $state_dir/opt_m) and testing for that. Users are oddly upset
> when their expectations are broken... (and I actually agree with them.)
I agree users are upset when expectations are broken, but why would
they expect REBASE-m? In fa
From: Johannes Schindelin
We really only need the test helpers to be built in the worktree in that
case, but that is not what we test for.
On the other hand it is a perfect opportunity to verify that
`GIT_TEST_INSTALLED` points to a working Git.
So let's test the appropriate Git executable
From: Johannes Schindelin
It makes very, very little sense to test the built git-sh-i18n when the
user asked specifically to test another one.
Signed-off-by: Johannes Schindelin
---
t/lib-gettext.sh | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/t/lib-gettext.sh b/t
From: Johannes Schindelin
Currently, we parse the options intended for `git am` as if we wanted to
handle them in `git rebase`, and then reconstruct them painstakingly to
define the `git_am_opt` variable.
However, there is a much better way (that I was unaware of, at the time
when I mentored
s to
> > > break the error reporting
> > >
> > > Running
> > >bin/wrappers/git rebase --onto @ @^^ -Cbad
> > >
> > > Gives
> > >git encountered an error while preparing the patches to replay
> > >these revi
Hi Peff,
On Wed, 14 Nov 2018, Jeff King wrote:
> On Mon, Nov 12, 2018 at 05:48:37AM -0800, Johannes Schindelin via
> GitGitGadget wrote:
>
> > diff --git a/t/test-lib.sh b/t/test-lib.sh
> > index 832ede5099..1ea20dc2dc 100644
> > --- a/t/test-lib.sh
> > +++ b
the test for now when we know that we want to
> > test an installed Git.
>
> True, but... hopefully we are making sure t/helpers/ has been built
> in some other ways, though, right?
We do it implicitly, in the test cases that use the helpers.
However, t/test-lib.sh does not particu
On Wed, Nov 14, 2018 at 12:31:22PM +, Luke Diamand wrote:
> On Fri, 9 Nov 2018 at 10:48, Jeff King wrote:
> >
> > On Fri, Nov 09, 2018 at 10:44:10AM +, Luca Milanesio wrote:
> >
> > > > On 9 Nov 2018, at 10:42, Jeff King wrote:
> > > >
> &
On Mon, Nov 12, 2018 at 05:48:37AM -0800, Johannes Schindelin via GitGitGadget
wrote:
> diff --git a/t/test-lib.sh b/t/test-lib.sh
> index 832ede5099..1ea20dc2dc 100644
> --- a/t/test-lib.sh
> +++ b/t/test-lib.sh
> @@ -51,7 +51,7 @@ expo
On Fri, 9 Nov 2018 at 10:48, Jeff King wrote:
>
> On Fri, Nov 09, 2018 at 10:44:10AM +, Luca Milanesio wrote:
>
> > > On 9 Nov 2018, at 10:42, Jeff King wrote:
> > >
> > > Git Merge 2019 is happening on February 1st. There will be a
> > &
Đoàn Trần Công Danh writes:
> -#ifndef NO_SYS_POLL_H
> +#if !defined(NO_POLL_H)
> +#include
> +#elif !defined(NO_SYS_POLL_H)
> #include
> #else
> +/* Pull the compat stuff */
> #include
> #endif
The last comment would help readers who got "Huh? When NO_POLL_H
and NO_SYS_POLL_H is
"brian m. carlson" writes:
>> - t1308.23 is failing because musl `fopen` is success when open directory
>> in readonly mode. POSIX allows this behavior:
>> http://pubs.opengroup.org/onlinepubs/7908799/xsh/fopen.html
>> [EISDIR]
>> The named file is a directory and mode requires write access.
>
>
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> We really only need the test helpers in that case, but that is not what
> we test for. So let's skip the test for now when we know that we want to
> test an installed Git.
True, but... hop
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> It makes very, very little sense to test the built git-sh-i18n when the
> user asked specifically to test another one.
>
> Signed-off-by: Johannes Schindelin
> ---
Yup. Makes
"brian m. carlson" writes:
> On Wed, Nov 14, 2018 at 08:10:43AM +0700, Đoàn Trần Công Danh wrote:
>> POSIX specifies that is the correct header for poll(2)
>> whereas is only needed for some old libc.
>>
>> Let's follow the POSIX way by default.
>>
>> This effectively eliminates musl's
On Wed, Nov 14, 2018 at 08:10:43AM +0700, Đoàn Trần Công Danh wrote:
> POSIX specifies that is the correct header for poll(2)
> whereas is only needed for some old libc.
>
> Let's follow the POSIX way by default.
>
> This effectively eliminates musl's warning:
>
> warning redirecting
ISO-2022-JP, yet.
https://wiki.musl-libc.org/functional-differences-from-glibc.html#iconv
Makefile | 8 +++-
configure.ac | 6 ++
git-compat-util.h | 5 -
3 files changed, 17 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index bbfbb4292..5734efe74 100644
Signed-off-by: Elijah Newren
---
Documentation/git-fast-import.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-fast-import.txt
b/Documentation/git-fast-import.txt
index e81117d27f..7ab97745a6 100644
--- a/Documentation/git-fast-import.txt
+++ b
Signed-off-by: Elijah Newren
---
Documentation/git-fast-export.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-fast-export.txt
b/Documentation/git-fast-export.txt
index ce954be532..fda55b3284 100644
--- a/Documentation/git-fast-export.txt
+++ b
On Tue, Nov 13, 2018 at 3:39 PM Jonathan Nieder wrote:
> Elijah Newren wrote:
> > Actually, no, it actually needs to be inconsistent.
> >
> > Different Input Choices (neither backslashed, both backslashed, then just
> > one):
> > master~9 and master~10
> > master\~9 and master\~10
> >
+git@vger.kernel.org, git-secur...@googlegroups.com -> bcc
Paul J Sanchez wrote:
> On Nov 13, 2018, at 2:25 PM, Stefan Beller wrote:
>> The link seems to be https://aurees.com/ ?
>>
>> They seem to have
>> https://aurees.com/legal/license-agreement
>> which
Elijah Newren wrote:
> Actually, no, it actually needs to be inconsistent.
>
> Different Input Choices (neither backslashed, both backslashed, then just
> one):
> master~9 and master~10
> master\~9 and master\~10
> master\~9 and master~10
>
> What the outputs look like:
> master9 and
On Sat, Nov 10, 2018 at 11:17 PM Elijah Newren wrote:
>
> On Sat, Nov 10, 2018 at 10:36 PM Jeff King wrote:
> >
> > On Sat, Nov 10, 2018 at 10:23:04PM -0800, Elijah Newren wrote:
> >
> > > Signed-off-by: Elijah Newren
> > > ---
> > > Docu
+cc: git@vger.kernel.org, git-secur...@googlegroups.com -> bcc
Hi!
Paul J Sanchez wrote:
> Over the weekend I saw a link to a Mac git client I had not seen
> before: Aurees. When I went to the linked site to download a copy,
> my antivirus software (Sophos) warned me that it cont
On Mon, 12 Nov 2018 at 00:47, Mateusz Loskot wrote:
>
> Hi,
>
> I'm posting here for the first time and I hope it's the right place to ask
> questions about Git LFS.
>
> TL;TR: Is this normal a repository migrated to Git LFS inflates multiple times
> and how to deal with
Hi Johannes
On 13/11/2018 19:21, Johannes Schindelin wrote:
Hi Phillip,
On Tue, 13 Nov 2018, Phillip Wood wrote:
Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems to
break the error reporting
Running
bin/wrappers/git rebase --onto @ @^^ -Cbad
Gives
git
Hi Phillip,
On Tue, 13 Nov 2018, Phillip Wood wrote:
> Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems to
> break the error reporting
>
> Running
> bin/wrappers/git rebase --onto @ @^^ -Cbad
>
> Gives
> git encountered an error whi
Here is the test coverage report for today.
Thanks,
-Stolee
[1] https://dev.azure.com/git/git/_build/results?buildId=256=logs
---
pu: a849d4c48bb308cdf3f9d7dc84251d92b4d7ff03
jch: e3cb78b4131db2f98330ff110525db31c6abff16
next: 17fedb746fde9e40924a6ce11c0976a097eb126b
master
quite a bit of
> work to do, but you already did most of it.
>
> Out of curiosity, do you have a public repository with these patches in a
> branch? (I might have an hour to play with it tonight...)
https://github.com/newren/git/tree/rebase-new-default, but ignore the
last two commits;
Hi Johannes
Thanks for looking at this. Unfortunately using OPT_PASSTHRU_ARGV seems
to break the error reporting
Running
bin/wrappers/git rebase --onto @ @^^ -Cbad
Gives
git encountered an error while preparing the patches to replay
these revisions
"" },
> - OPT_STRING_LIST(0, "whitespace", ,
> - N_("whitespace"), N_("passed to 'git apply'")),
> - OPT_SET_INT('C', NULL, _c, N_("passed to 'git apply'"),
> -
From: Johannes Schindelin
Currently, we parse the options intended for `git am` as if we wanted to
handle them in `git rebase`, and then reconstruct them painstakingly to
define the `git_am_opt` variable.
However, there is a much better way (that I was unaware of, at the time
when I mentored
Hi Junio,
On Tue, 13 Nov 2018, Junio C Hamano wrote:
> "Johannes Schindelin via GitGitGadget"
> writes:
>
> > From: Johannes Schindelin
> >
> > The scripted version of the rebase used to execute `git reset --hard`
> > when skipping or aborti
Denton Liu writes:
> This adds the --save-to-push option to `git remote set-url` such that
> when executed, we move the remote.*.url to remote.*.pushurl and set
> remote.*.url to the given url argument.
>
> For example, if we have the following config:
>
>
gt; >> special strategy options. As such, there really is not any need for
> >> having both git-rebase--merge and git-rebase--interactive anymore.
> >>
> >> Delete git-rebase--merge.sh and have the --merge option be implemented
> >> by the now built-in inte
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> The scripted version of the rebase used to execute `git reset --hard`
> when skipping or aborting. When we ported this to C, we did update the
> worktree and some reflogs, but we failed to
On Mon, 12 Nov 2018 at 13:31, Jeff King wrote:
> On Mon, Nov 12, 2018 at 12:47:42AM +0100, Mateusz Loskot wrote:
> >
> > TL;TR: Is this normal a repository migrated to Git LFS inflates multiple
> > times
> > and how to deal with it?
>
> That does sound odd to me
From: Johannes Schindelin
The scripted version of the rebase used to execute `git reset --hard`
when skipping or aborting. When we ported this to C, we did update the
worktree and some reflogs, but we failed to imitate `git reset --hard`'s
behavior regarding files in .git/ such as MERGE_HEAD
I use git add -e frequently. Often there are multiple hunks and I end up
deleting the + lines and converting the - lines to context lines, as I like
to stage massive changes in an incremental fashion (and commit those staged
changes incrementally, too).
Some time after I invented git add -e
Hi Fredi,
Fredi Fowler wrote:
> Is there any way to create pull request to git man (https://git-scm.com/docs)?
>
> I found there some inconsistencies. For example, almost in all pages
> are using [no-], but at https://git-scm.com/docs/git-merge each
> command (with [no-] or
rms of cherry-pick rather than
>> the merge-recursive builtin, but cherry-pick also calls into the recursive
>> merge machinery by default and can accept special merge strategies and/or
>> special strategy options. As such, there really is not any need for
>> having both git
> special strategy options. As such, there really is not any need for
> having both git-rebase--merge and git-rebase--interactive anymore.
>
> Delete git-rebase--merge.sh and have the --merge option be implemented
> by the now built-in interactive machinery.
Okay.
> Note that this ch
; On Sun, Sep 23, 2018 at 6:08 AM Lars Schneider
> >> > wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> I recently had to purge files from large Git repos (many files, many
> >> >> commits).
> >> >> Th
up an editor. The rewrite of interactive rebase in C
> added a quiet option, though it only turns stats off. Since we want to
> make the interactive machinery also take over for git-rebase--merge, it
> should fully implement the --quiet option.
>
> git-rebase--interactive was already
From: Johannes Schindelin
We really only need the test helpers in that case, but that is not what
we test for. So let's skip the test for now when we know that we want to
test an installed Git.
Signed-off-by: Johannes Schindelin
---
t/test-lib.sh | 2 +-
1 file changed, 1 insertion(+), 1
From: Johannes Schindelin
It makes very, very little sense to test the built git-sh-i18n when the
user asked specifically to test another one.
Signed-off-by: Johannes Schindelin
---
t/lib-gettext.sh | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/t/lib-gettext.sh b/t
Hi Ævar,
On Fri, 2 Nov 2018, Ævar Arnfjörð Bjarmason wrote:
> * GIT_TEST_INSTALLED breaks entirely under this, as early as the
>heuristic for "are we built?" being "do we have git-init in
>libexecdir?". I tried a bit to make this work, but there's a lot o
Hi,
Thank you very much!
The git-bug project is what I'm looking for even if it is not very interesting
without gitlab connection.
There is an issue about it on Gitlab:
https://gitlab.com/gitlab-org/gitlab-ce/issues/50435
Maybe some encouragment from git core developer would help!
I also
On Mon, Nov 12 2018, Jeff King wrote:
> On Mon, Nov 12, 2018 at 12:47:42AM +0100, Mateusz Loskot wrote:
>
>> Hi,
>>
>> I'm posting here for the first time and I hope it's the right place to ask
>> questions about Git LFS.
>>
>> TL;TR: Is this normal
On Mon, Nov 12, 2018 at 12:47:42AM +0100, Mateusz Loskot wrote:
> Hi,
>
> I'm posting here for the first time and I hope it's the right place to ask
> questions about Git LFS.
>
> TL;TR: Is this normal a repository migrated to Git LFS inflates multiple times
On Sun, Nov 11, 2018 at 11:50:00PM +0100, Martin Delille wrote:
> This would be awesome to handle issue directly with git: Having an
> offline version of the issues synced to the gitlab/github issues. A
> lot of work is done on the issues and it is lost when migrating from
>
On Mon, Nov 12 2018, Konstantin Khomoutov wrote:
> On Mon, Nov 12, 2018 at 09:35:31AM +0800, yan ke wrote:
>
>> > This would be awesome to handle issue directly with git:
>> > Having an offline version of the issues synced to the gitlab/github issues.
>> > A
Hi,
>> >>
>> >> I recently had to purge files from large Git repos (many files, many
>> >> commits).
>> >> The usual recommendation is to use `git filter-branch --index-filter` to
>> >> purge
>> >> files. However, this is *ver
On Mon, Nov 12, 2018 at 09:35:31AM +0800, yan ke wrote:
> > This would be awesome to handle issue directly with git:
> > Having an offline version of the issues synced to the gitlab/github issues.
> > A lot of work is done on the issues and it is lost when migrating
&g
the git issue track!
Martin Delille 于2018年11月12日周一 上午6:52写道：
>
> Hi,
>
> This would be awesome to handle issue directly with git:
> Having an offline version of the issues synced to the gitlab/github issues.
> A lot of work is done on the issues and it is lost when migrating f
Hi,
I'm posting here for the first time and I hope it's the right place to ask
questions about Git LFS.
TL;TR: Is this normal a repository migrated to Git LFS inflates multiple times
and how to deal with it?
I'm migrating a big SVN repository to Git.
In SVN, a collection of third-party SDKs
Hi,
This would be awesome to handle issue directly with git:
Having an offline version of the issues synced to the gitlab/github issues.
A lot of work is done on the issues and it is lost when migrating from one
service to the other.
Beside we don’t always have a good internet connection
I was afraid that was the reason. Oh well, at least we know why :-)
Thanks Ævar!
Best-F
> On Nov 11, 2018, at 9:00 AM, Ævar Arnfjörð Bjarmason wrote:
>
>
>> On Sun, Nov 11 2018, Federico Lucifredi wrote:
>>
>> git clone of non-existent repository results
On Sun, Nov 11 2018, Federico Lucifredi wrote:
> git clone of non-existent repository results in request for credentials
>
> REPRODUCING:
> sudo apt install git
> git clone https://github.com/xorbit/LiFePo4owered-Pi.git#this repo does
> not exist
>
> Git will
git clone of non-existent repository results in request for credentials
REPRODUCING:
sudo apt install git
git clone https://github.com/xorbit/LiFePo4owered-Pi.git#this repo does not
exist
Git will then prompt for username and password on Github.
I can see a valid data-leak concern (one
On Sat, Nov 10, 2018 at 10:36 PM Jeff King wrote:
>
> On Sat, Nov 10, 2018 at 10:23:04PM -0800, Elijah Newren wrote:
>
> > Signed-off-by: Elijah Newren
> > ---
> > Documentation/git-fast-export.txt | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
&
On Sat, Nov 10, 2018 at 10:23:04PM -0800, Elijah Newren wrote:
> Signed-off-by: Elijah Newren
> ---
> Documentation/git-fast-export.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/git-fast-export.txt
> b/Documentation/git-fa
On Sat, Nov 10, 2018 at 10:23:03PM -0800, Elijah Newren wrote:
> Signed-off-by: Elijah Newren
> ---
> Documentation/git-fast-import.txt | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-fast-import.txt
> b/Documentatio
Signed-off-by: Elijah Newren
---
Documentation/git-fast-export.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-fast-export.txt
b/Documentation/git-fast-export.txt
index ce954be532..677510b7f7 100644
--- a/Documentation/git-fast-export.txt
+++ b
Signed-off-by: Elijah Newren
---
Documentation/git-fast-import.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-fast-import.txt
b/Documentation/git-fast-import.txt
index e81117d27f..7ab97745a6 100644
--- a/Documentation/git-fast-import.txt
+++ b
On Sat, Nov 10, 2018 at 7:21 PM Fredi Fowler wrote:
> Is there any way to create pull request to git man (https://git-scm.com/docs)?
That website is maintained as a project separate from Git, so you can
report issues specific to the website, or create pull requests, at its
project page (ht
Is there any way to create pull request to git man (https://git-scm.com/docs)?
I found there some inconsistencies. For example, almost in all pages
are using [no-], but at https://git-scm.com/docs/git-merge each
command (with [no-] or without) write separately.
There are some same
Hi Alban,
On Fri, 9 Nov 2018, Alban Gruin wrote:
> p3400 makes a copy of the current repository to test git-rebase
> performance, and creates new branches in the copy with `git checkout
> -b'. If the original repository has branches with the same name as the
> script is tryi
p3400 makes a copy of the current repository to test git-rebase
performance, and creates new branches in the copy with `git checkout
-b'. If the original repository has branches with the same name as the
script is trying to create, this operation will fail.
This replaces these calls by `git
Hi,
On Tue, 2 Oct 2018, Ævar Arnfjörð Bjarmason wrote:
> On Tue, Oct 02 2018, Taylor Blau wrote:
>
> > Hi Stefan,
> >
> > On Sat, Sep 29, 2018 at 04:00:04PM -0700, Stefan Xenos wrote:
> >> Hello, List!
> >>
> >> I'm interested in porting so
On Fri, Nov 09, 2018 at 10:44:10AM +, Luca Milanesio wrote:
> > On 9 Nov 2018, at 10:42, Jeff King wrote:
> >
> > Git Merge 2019 is happening on February 1st. There will be a
> > Contributor's Summit the day before. Here are the details:
> >
> > When:
> On 9 Nov 2018, at 10:42, Jeff King wrote:
>
> Git Merge 2019 is happening on February 1st. There will be a
> Contributor's Summit the day before. Here are the details:
>
> When: Thursday, January 31, 2019. 10am-5pm.
> Where: The Egg[1], Brussels, Belgium
> What
Git Merge 2019 is happening on February 1st. There will be a
Contributor's Summit the day before. Here are the details:
When: Thursday, January 31, 2019. 10am-5pm.
Where: The Egg[1], Brussels, Belgium
What: Round-table discussion about Git
Who: All contributors to Git or related projects
This adds the --save-to-push option to `git remote set-url` such that
when executed, we move the remote.*.url to remote.*.pushurl and set
remote.*.url to the given url argument.
For example, if we have the following config:
[remote "origin"]
url = g...@gith
Denton Liu writes:
> This adds the --save-push option to `git remote set-url` such that when
> executed, we move the remote.*.url to remote.*.pushurl and set
> remote.*.url to the given url argument.
>
> For example, if we have the following config:
>
>
This adds the --save-push option to `git remote set-url` such that when
executed, we move the remote.*.url to remote.*.pushurl and set
remote.*.url to the given url argument.
For example, if we have the following config:
[remote "origin"]
url = g...@github.com:g
bed in the PR), and the problem is not directly related to
> rebasing, so I considered it better in order to avoid unrelated
> confusions.
>
> Let's get back to the problem. Each system has a default endianness.
> Also, in .gitattributes's working-tree-encoding, Git behaves
&g
both git-rebase--merge and git-rebase--interactive anymore.
Delete git-rebase--merge.sh and have the --merge option be implemented
by the now built-in interactive machinery.
Note that this change fixes a few known test failures (see t3421).
testcase modification notes:
t3406: --interactive
it only turns stats off. Since we want to
make the interactive machinery also take over for git-rebase--merge, it
should fully implement the --quiet option.
git-rebase--interactive was already somewhat quieter than
git-rebase--merge and git-rebase--am, possibly because cherry-pick has
just
Here is the coverage report for today.
Thanks,
-Stolee
[1] https://dev.azure.com/git/git/_build/results?buildId=251=logs
---
pu: 381b31f0006e46fe041e7fc6e5f7b19da5ccd889
jch: ab76604d6537afa18c9d8588c08f699c1f539659
next: 8438c0b2453a7207c9c45756f5e37dfe283db602
master
r to avoid unrelated
confusions.
Let's get back to the problem. Each system has a default endianness.
Also, in .gitattributes's working-tree-encoding, Git behaves
differently depending on the attribute's value and the contents of the
referenced entry file. When I put the value "UTF-16", the
On Mon, Nov 05, 2018 at 07:10:14PM +0100, Torsten Bögershausen wrote:
> On Mon, Nov 05, 2018 at 05:24:39AM +0100, Adrián Gimeno Balaguer wrote:
>
> []
>
> > https://github.com/git/git/pull/550
>
> []
>
> > This is covered in the mentioned PR above.
rom this bug.
Used Version: 1:2.17.1-1ubuntu0.3
OS: Ubuntu 16.04.5 LTS
Commandline: /usr/bin/git svn clone --prefix= --preserve-empty-dirs
--authors-file=/mnt/migration/authors.txt --stdlayout https://host/repo
/mnt/migration/repos/TES
i, Nov 02, 2018 at 11:10:51AM -0500, Peter Kostyukov wrote:
> >> Wanted to bring to your attention an issue that we discovered on our
> >> Windows Jenkins nodes with git scm installed (git.exe). Our Jenkins
> >> servers don't have Internet access. It appears that gi
301 - 400 of 30258 matches
Mail list logo
