On Thu, Sep 22, 2016 at 12:54:57PM +0100, Aaron Gray wrote:
> I am having problems cloning a 2.1GB repo from googlesource
>
> C:\Users\Aaron Gray\GitHub>git clone
> https://chromium.googlesource.com/chromium/chromium
> Cloning into 'chromium'...
> remote: Sending approximately 2.11 GiB ...
> error
On Fri, Sep 23, 2016 at 12:15:41AM -0400, Jeff King wrote:
> On Thu, Sep 22, 2016 at 03:17:23PM -0700, Junio C Hamano wrote:
>
> > Jeff King writes:
> >
> > > On Mon, Sep 19, 2016 at 08:54:40PM +0200, Kevin Daudt wrote:
> > >
> > >&g
Many tests need to store data in a file, and repeat the same pattern to
refer to that path:
"$TEST_DIRECTORY"/t5100/
Create a variable that contains this path, and use that instead.
Signed-off-by: Kevin Daudt
Signed-off-by: Junio C Hamano
---
Changes since v2:
- changed $DAT
so that they don't
show up in the author field.
Signed-off-by: Kevin Daudt
Signed-off-by: Junio C Hamano
---
Changes since v2:
- handle comments inside comments recursively
- renamed the main function to unquote_quoted_pairs because it also
handles quoted pairs in comments
maili
On Mon, Sep 26, 2016 at 12:38:42AM +0200, Jakub Narębski wrote:
> W dniu 25.09.2016 o 22:17, Kevin Daudt pisze:
> > On Fri, Sep 23, 2016 at 12:15:41AM -0400, Jeff King wrote:
>
> >> Oops, yes. It is beginning to make the "strbuf_swap()" look less
> >> convo
On Mon, Sep 26, 2016 at 12:26:13PM -0700, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> > Don't these also need to be downcased if you prefer $data over
> > $DATA, though?
>
> For now, I'll queue a SQUASH??? that reverts s/DATA/data/ you did to
> 1/2 between your 1/2 and 2/2.
>
Ugh, thank
On Mon, Sep 26, 2016 at 03:23:23PM -0700, Junio C Hamano wrote:
> Kevin Daudt writes:
>
> > On Mon, Sep 26, 2016 at 12:26:13PM -0700, Junio C Hamano wrote:
> >> Junio C Hamano writes:
> >>
> >> > Don't these also need to be downcase
On Fri, Sep 16, 2016 at 01:53:15PM -0700, Junio C Hamano wrote:
> Kevin Wern writes:
>
> > Create git-prime-clone, a program to be executed on the server that
> > returns the location and type of static resource to download before
> > performing the rest of a clone.
>
On Fri, Sep 16, 2016 at 03:17:28PM -0700, Junio C Hamano wrote:
> Kevin Wern writes:
>
> > /* And complain if we didn't get enough bytes to satisfy the read. */
> > if (ret < size) {
> > - if (options & PACKET_READ_GENTLE
On Mon, Sep 19, 2016 at 08:15:00PM +0700, Duy Nguyen wrote:
> We also have an exception for select_getanyfile() below. I think it's
> time we add a function callback in struct rpc_service to run each
> service the way they want. Then prime-clone won't need an exception
> (neither does select_anyfil
On Mon, Sep 19, 2016 at 09:04:40PM +0700, Duy Nguyen wrote:
> On Fri, Sep 16, 2016 at 7:12 AM, Kevin Wern wrote:
> > builtin/clone.c | 590
> > +---
>
> Argh.. this is too big for my brain at this hour. It might be easi
On Fri, Sep 16, 2016 at 04:07:00PM -0700, Junio C Hamano wrote:
> Kevin Wern writes:
>
> > Add option RUN_COMMAND_NO_STDOUT, which sets no_stdout on a child
> > process.
> >
> > This will be used by git clone when calling index-pack on a downloaded
> > pac
ou got in the bundle and the reality that has progressed
> since the primer pack was made, and you need a way to tell to the
> other end that you already have the history leading to these refs
> when you run "git fetch". I think a bit better way to do so is to
> send these has ".have" while you run the "fetch".
>
> Wouldn't it do if you add the "--advertise-bundle-tips="
> option to "git fetch", move the code to read the bundle header to
> it, and point the bundle's filename with the option when you spawn
> "git fetch"?
My implementation is definitely a minimum working model. I was hoping to
move to something cleaner.
Is this new option preferable to leveraging the "--reference" option you
mentioned in the earlier discussion? I thought that was a clean solution,
especially because it uses an existing option. Additionally, would there be
any use for this new fetch option outside of cloning? If so, I could see the
value--otherwise, knowing that we want to keep as much resume-specific
knowledge inside clone as possible, "--reference" with a .bndl seems better.
- Kevin
ow curl has a --retry option,
but doesn't include it in libcurl...harumph. I'll probably try to read that
implementation and chromium's resumable download code again.
I'll get back to you with a better plan here once I read through a few
examples.
- Kevin
don't know anything about
> the server side (and on top of that I was confused between http
> send/receive vs transport send/receive, but this is my fault).
>
I figured I would miss something in this vein. So many things to cover!
Thanks again for reading.
- Kevin
On Wed, Sep 28, 2016 at 10:54:52AM -0700, Junio C Hamano wrote:
>
> I just got an impression that you were apologetic for having to add
> this option that is otherwise useless and tried to suggest a simpler
> solution that does not involve such an addition.
Sorry, to be clear, I meant I was ok wi
Changes since v3:
- t5100-mailinfo: Reverted back to capital $DATA
- t5100-mailinfo: Moved quotes to around the entire string, instead of the
variable, as per Junio's suggestion
Kevin Daudt (2):
t5100-mailinfo: replace common path prefix with variable
mailinfo: unescape quoted-pa
don't
show up in the author field.
Signed-off-by: Kevin Daudt
Signed-off-by: Junio C Hamano
---
mailinfo.c | 82
t/t5100-mailinfo.sh | 14
t/t5100/comment.expect | 5 +++
t/t5100/comment.in
ound the entire string to not give the impression
we want shell splitting to affect the other variables.
Signed-off-by: Kevin Daudt
Signed-off-by: Junio C Hamano
---
t/t5100-mailinfo.sh | 68 +++--
1 file changed, 35 insertions(+), 33 deletions(-)
On Wed, Sep 28, 2016 at 01:21:13PM -0700, Junio C Hamano wrote:
> Kevin Daudt writes:
>
> > Many tests need to store data in a file, and repeat the same pattern to
> > refer to that path:
> >
> > "$TEST_DIRECTORY"/t5100/
> >
> > Create a va
On Sat, Oct 01, 2016 at 12:24:57AM +0200, Jakub Narębski wrote:
>
> | 7.2.1 Discussion
> [...]
> | There could be other use cases for the
> | staging area that Gitless doesn’t handle well but we expect
> | these to be fairly infrequent.
>
> Like handling merge conflict...??? Infrequent doesn't me
doing
that in the compiler explorer - it effectively turns that into "else
if". To make that check really work, you have to do:
if (array)
qsort(array, nmemb, size, cmp);
else
printf("array is NULL\n");
So maybe your "sane_qsort" should be checking array, not nmemb.
Kevin
27;ve called qsort on it, you've invoked undefined behaviour if it's
NULL, so it's free to elide the NULL check.
Kevin
On 04/10/2016 01:00, René Scharfe wrote:
Am 03.10.2016 um 19:09 schrieb Kevin Bracey:
As such, NULL checks can still be elided even with your change. If you
effectively change your example to:
if (nmemb > 1)
qsort(array, nmemb, size, cmp);
if (!array)
printf("
st.txt already exists, no checkout
Could not restore untracked files from stash
So the user must remove it themselves, which can be confusing since
the file is not listed in `git stash show`, which doesn't include
untracked files.
Kevin
P.S. Please CC me on replies. Thanks!
--
To un
p or apply produces the following output:
$ git stash pop --quiet
Already up-to-date!
It's obviously a minor issue, but can be an annoyance for scripting
tasks.
Thanks for considering,
Kevin
P.S. Please CC me on replies. Thanks!
--
To unsubscribe from this list: send the line "unsubscr
subscribe git
--
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 Mon, Feb 22, 2016 at 05:24:15PM +0530, Nagaraj Mandya wrote:
> Hello,
> In our GIT repository, all users are restricted from merging to
> master without a pull request. This works well and all developers are
> raising pull requests and merging. However, if there is a merge
> conflict during th
On Sat, Feb 06, 2016 at 10:56:46PM +0100, Ole Tange wrote:
> git diff first looks for a file, then looks if it is a reference to a
> revision. If the file fails due to being too long, the diff fails:
>
> $ git init
> $ git diff
> 'HEAD^^
On Tue, Feb 23, 2016 at 11:57:06PM +0100, Moritz Neeb wrote:
> On 02/23/2016 06:39 PM, Seb wrote:
> > On Sun, 21 Feb 2016 03:12:49 +0100,
> > Moritz Neeb wrote:
> >
> >> Hi Seb,
> >> On 02/20/2016 11:58 PM, Seb wrote:
> >>> Hello,
> >
> >>> I've recently learnt how to consolidate and clean up th
On Wed, Feb 24, 2016 at 04:38:11PM -0700, Bill Okara wrote:
> Hi,
>
> I noticed the following 'git mv' issue with:
> git version 2.6.4
>
>
> If there are identical files in different subfolders, 'git mv' the
> root folder (and/or each file individually) will mess up the file path
> mapping. that
On Fri, Feb 26, 2016 at 02:18:16PM +, Gerald wrote:
> I have git running on a VMware virtual machine. I backup the virtual
> machine every day. How do I restore git from a restore of the virtual
> machine?
>
Can you explain what you mean exactly with restoring git? It's unclear
what you wa
riginal Message-
> From: Kevin Daudt [mailto:m...@ikke.info]
> Sent: Friday, February 26, 2016 11:44 AM
> To: Gerald McKinley
> Cc: git@vger.kernel.org
> Subject: Re: Restore Question
>
> On Fri, Feb 26, 2016 at 02:18:16PM +, Gerald wrote:
> > I have git running
happening
Signed-off-by: Kevin Daudt
---
builtin/revert.c| 2 ++
sequencer.c | 21 -
sequencer.h | 1 +
t/t3510-cherry-pick-sequence.sh | 12
4 files changed, 31 insertions(+), 5 deletions(-)
diff --git a
On Tue, Mar 01, 2016 at 02:49:58PM -0800, Stefan Beller wrote:
> The wording is introduced in c3f0baaca (Documentation: sync git.txt
> command list and manual page title, 2007-01-18), but rebase has evolved
> since then, capture the modern usage by being more generic about the
> rebase command in t
git commit has a --no-verify option to prevent the pre-commit hook from
running. When continuing a conflicted cherry-pick, git commit gets
executed which also causes the pre-commit hook to be run.
Add --no-verify and pass that through to the git commit command.
Signed-off-by: Kevin Daudt
On Tue, Mar 01, 2016 at 12:01:53PM +0100, greg0ire wrote:
> Hello,
>
> using git 2.1.4 here, and it seems there is no option to bypass pre-commit
> hooks while cherry-picking, while git commit provides a --no-verify option.
> I ended up doing this to disable hooks while cherry picking :
>
> t
On Thu, Mar 03, 2016 at 09:11:56PM -0500, Charles Strahan wrote:
> Hello,
>
> I've found a change in the way .gitignore works, and I'm not sure if
> it's a bug
> or intended.
>
> Previously, one could use the following .gitignore:
>
> *
> !/foo
> !/foo/bar.txt
> !/baz
> !/baz
xclude everything except directory foo/bar
> /*
> !/foo
> /foo/*
> !/foo/bar
>
> Note the /foo/*, explicitly ignoring the entries below /foo.
>
> This wasn't always the case, though, so I'd love to hear if it was
> intentional
> (or if I'
ng
at relevant code yesterday to start working on it.
Is someone working on this currently? Are there any things I should
know moving forward? Is there a certain way I should break
down/organize the feature when writing patches?
Any information is appreciated.
Thanks,
Kevin
--
To unsubscribe from this
On Mon, Mar 07, 2016 at 10:01:52PM +0300, Olga Pshenichnikova wrote:
> I have some tree structure:
>
> /a
> /a/a
> /a/b
> ..
> /a/z
> /b
> .. (thousands of folders)
> /z
>
> How can I control just /a/a folder?
> What exclude file should be?
>
> The way we use now is:
>
> /a/*
> /b/
> .. (thousa
Hey Junio and Duy,
Thank you for your thorough responses! I'm new to git dev, so it's
extremely helpful.
> - The server side endpoint does not have to be, and I think it
> should not be, implemented as an extension to the current
> upload-pack protocol. It is perfectly fine to add a new "git
> pr
ion that no follow-up fetch is
> allowed, which requires you to limit yourself to "full" history,
> which is an unnecessary requirement) are good points one should be
> making design decisions on when building this part of the system.
Awesome, all of this is enough info to get me started. Thanks!
Kevin
--
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 Mon, Mar 14, 2016 at 12:03:33AM +0530, Sidhant Sharma wrote:
>
>
>
> Other than this, I also tried to expand the list of potentially destructive
> commands and updated the list as follows (additions in brackets):
>
> * git rebase [ git pull --rebase ]
> * git reset --hard
> * git clean -f
>
thout duplicating diff-options.txt,
hopefully someone will be more inspired than me ;)
Thanks,
Kevin
--
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 Sun, Oct 18, 2015 at 04:32:24PM +0530, Sidhant Sharma wrote:
> Mark as optional in worktree command line usage.
Thank you for the patch.
Can you also explain why you mark it as optional in the commit message?
That way it's clear why this patch is needed.
>
> Hi, just starting out with de
default:
- assert_not_reached("Unknown argument");
+ assert_not_reached("Unkown argument");
}
+}
If you look at the lines with assert_not_reached, it seems there is a
difference in t
On Fri, Jan 18, 2019 at 10:40:55PM +, Eric Wong wrote:
> Steve Keller wrote:
> > $ git reflog expire --all
>
> I've never used "git reflog" directly, but I think you need to
> add "--expire=all" to cover all time. "--all" is only for all
> branches, so you need "--expire=" is for a time
ject.
You can find details on how to provide translations here[0]. It looks
from that document that someone started translating the book in Turkish
as well[1].
Kind regards, Kevin
[0]:https://github.com/progit/progit2/blob/master/TRANSLATING.md
[1]:https://github.com/progit/progit2-tr
ady exists."
>
> Once the branch is created, you can't force its creation, because it is
> already created. Just
>
> git checkout "branch_name"
>
> is sufficient at this point. git is correct to complain that you are trying
> to create a branch that already exists.
git checkout -B exists, which does exactly that: force create a branch
at a new positon if it already exists.
Kind regards, Kevin
o stderr is more treated like an additional output stream rather than
only reporting errors to stderr.
Hope this helps, Kevin
>
> --
> Thomas Hruska
> CubicleSoft President
>
> http://cubiclesoft.com/
>
On Thu, Jul 11, 2019 at 03:11:33PM -0500, Robert Morgan wrote:
> subscribe git
You need to send this to majord...@vger.kernel.org. Sending it to the
git mailing list will not do a lot.
Kevin
ing trivial? is the explanation misleading or inncomplete?
>
> rday
>
> --
>
After selecting 'p', what do you get?
You should see a list of modified files. You can select the files you
want to stage by the listed numbers. After you selected those files, you
press enter, and then you will get the options you'll also see with git
add -p.
Kevin
usr/local/ -name '*mailsplit*'
> /usr/local/share/doc/git-doc/git-mailsplit.txt
> /usr/local/share/doc/git-doc/git-mailsplit.html
> /usr/local/share/man/man1/git-mailsplit.1
> /usr/local/libexec/git-core/git-mailsplit
This is the mailsplit command, and should be executed when running `git
mailsplit`. What does git --exec-dir return?
Kevin
ield is not the number of extensions, but the number
of index entries.
I'm not sure why you are seeing so many index entries. I've just tested
it myself on the git repository and I got 3419 entries when reading in
network (big-endian) order.
Hope this helps a bit.
Kevin
On Mon, Jun 18, 2018 at 01:19:19PM +0200, Heiko Voigt wrote:
Now with cc to the mailing list.
> Hi,
>
> I just discovered that when you have a slash at the end of a nested
> repository, the files contained in the repository get added instead of
> the gitlink.
>
> I found this when I was adding
les of the cloned repository to the parent repo, and
basically ignore that it's another repository.
And I guess no one complained because it looked like a feature rather
than a bug.
Kevin
, all the other tests fail as well
as they expect the file to be present in the repository.
Any idea how to get around this?
Kevin
On Fri, Feb 08, 2019 at 11:45:02AM +, brian m. carlson wrote:
> On Fri, Feb 08, 2019 at 01:04:03AM -0500, Rich Felker wrote:
> [..]
> > In any case, this test seems mainly relevant to Windows users wanting
> > to store source files in UTF-16LE with BOM. This doesn't really make
> > sense to do
On Fri, Feb 08, 2019 at 09:50:07AM -0800, Junio C Hamano wrote:
> "brian m. carlson" writes:
>
> >> So would you suggest that we just skip this test on Alpine Linux?
> >
> > That's not exactly what I said. If Alpine Linux users are never going to
> > use this functionality and don't care that it'
On Fri, Feb 08, 2019 at 08:42:19PM +, brian m. carlson wrote:
> On Fri, Feb 08, 2019 at 09:23:36PM +0100, Kevin Daudt wrote:
> > Firstly, the tests expect iconv -t UTF-16 to output a BOM, which it
> > indeed does not do on Alpine. Secondly, git itself also expects the BOM
&g
#x27;, resulting in an
invalid BOM.
Fix this by using the proper value of 0xff: '\377'.
Signed-off-by: Kevin Daudt
---
I do wonder why this code is using octal values in the first place,
rather than using hex values.
t/t0028-working-tree-encoding.sh | 8
1 file changed, 4 i
On Mon, Feb 11, 2019 at 01:26:39AM +, brian m. carlson wrote:
> When serializing UTF-16 (and UTF-32), there are three possible ways to
> write the stream. One can write the data with a BOM in either big-endian
> or little-endian format, or one can write the data without a BOM in
> big-endian fo
undo the last operation. In my opinion this is
a better way to go then to add confirmations everywhere.
I know this has come up on the git mailing list more often, but I cannot
find a relevant thread at this moment.
Kevin
On Tue, Mar 12, 2019 at 01:22:51PM -0400, Robert P. J. Day wrote:
>
> never noticed this before ... when i do a regular "git commit" and
> enter my "vi" edit session and change my mind, i can bail with ":q!",
> regardless of what i've set up as a commit message, and i'll see:
>
> Aborting com
> fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
> remote = origin
> merge = refs/heads/master
> [submodule "src/libgp"]
> url = http://github.com/grumpy-irc/libgp
> [submodule "src/libirc"]
> url = http://github.com/grumpy-irc/libirc
> [branch "remote_scripts"]
> remote = origin
> merge = refs/heads/remote_scripts
>
Hello Petr,
What does git config --show-origin remoe.origin.url return?
Kind regards, Kevin
On Fri, Aug 23, 2019 at 10:43:45PM +0200, Albert Vaca Cintora wrote:
> Hi git folks,
>
> Honestly I'm not aware of the reason behind .git being read-only, but
> I'm sure there is one.
>
> However, I'm sure that a large percentage of developers out there will
> agree with me that having to use for
users.
In the #git irc channel we often have to explain what '--' means and
why it's sometimes necessary.
I don't however know a better solution to it more clear.
Kevin
On Tue, Nov 21, 2017 at 04:27:59PM -0500, Robert P. J. Day wrote:
> No major changes, just some rewording and showing some variations of
> general Git commands.
>
> Signed-off-by: Robert P. J. Day
>
> ---
>
> diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
> index 9f13266a6..d6
On Tue, Nov 21, 2017 at 04:47:42PM -0500, Robert P. J. Day wrote:
> On Tue, 21 Nov 2017, Kevin Daudt wrote:
>
> > On Tue, Nov 21, 2017 at 04:27:59PM -0500, Robert P. J. Day wrote:
> > > No major changes, just some rewording and showing some variations of
>
On Wed, Nov 22, 2017 at 06:19:23AM -0500, Robert P. J. Day wrote:
> On Wed, 22 Nov 2017, Junio C Hamano wrote:
>
> > "Robert P. J. Day" writes:
> >
> > > git repo with a file called "Gemfile", so i created a branch called
> > > "Gemfile", and when i ran:
> > >
> > > $ git checkout Gemfile
> > >
'--' to separate paths from revisions, like this:
'git [...] -- [...]'
There might be good reasons why this is, but I don't consider this to be
actually ambiguous: there is no branch called 'deleted_file.txt' and git
could know that the files exists in the mentioned commit, so it should
be pretty clear what is meant.
Might be worth documenting this.
Kevin
mp;&
> + git merge --verbose --ff-only side-signed >mergeoutput &&
> + test_i18ngrep "has a good GPG signature" mergeoutput &&
> + git checkout initial
> '
>
> test_expect_success GPG 'merge commit with bad signature without
> verification' '
> - git merge $(cat forged.commit)
> + git merge $(cat forged.commit) &&
> + git checkout initial
> +'
> +
> +test_expect_success GPG 'merge commit with bad signature with
> merge.verifySignatures=false' '
> + test_config merge.verifySignatures false &&
> + git merge $(cat forged.commit) &&
> + git checkout initial
> +'
> +
> +test_expect_success GPG 'merge commit with bad signature with
> merge.verifySignatures=true and --no-verify-signatures' '
> + test_config merge.verifySignatures true &&
> + git merge --no-verify-signatures $(cat forged.commit) &&
> + git checkout initial
> '
>
> test_done
Kevin.
On Sat, Dec 09, 2017 at 09:05:29AM +, Hans Jerry Illikainen wrote:
> Add tests for `pull --verify-signatures` with untrusted, bad and no
> signatures. Previously the only test for `--verify-signatures` was to
> make sure that `pull --rebase --verify-signatures` result in a warning
> (t5520-pul
On Sat, Dec 09, 2017 at 09:05:30AM +, Hans Jerry Illikainen wrote:
> Verify the signature of the tip commit when `pull.verifySignatures` is
> true. This option overrides `merge.verifySignatures` on pull, and can
> be disabled with the option `--no-verify-signatures`.
Is there a reason why git
it would be a lot of hassle for those
projects to get the sha1collisiondetection contents.
That's in my opinion a bigger disadvantage of submodules, commands like
git archive do not support it, making it harder to get self-contained
tarballs.
Perpahs there is a good solution to that problem, but then I'd like to
hear it.
Kevin.
On Sat, Dec 09, 2017 at 01:30:14PM +0100, Kevin Daudt wrote:
> On Tue, Dec 05, 2017 at 02:02:50AM -0500, Jeff King wrote:
> > On Tue, Nov 28, 2017 at 09:32:13PM +, Ævar Arnfjörð Bjarmason wrote:
> >
> > > Change the build process so that instead of needing to supply
On Fri, Dec 08, 2017 at 10:29:56PM +, Ævar Arnfjörð Bjarmason wrote:
> Here's v2 as promised. Comments per-patch.
>
> sha1dc: remove in favor of using sha1collisiondetection as a submodule
>
> Reword & expand commit message.
Is this commit missing from the mailing list because the e-mail i
ith that value then? Why does this change improve the
situation?
These are things you can state in your commit message.
Hope this helps, Kevin
> > Up until recently, we encouraged dropping the curly brackets from
> > single-line statements, but apparently that changed. It is
On Fri, Dec 29, 2017 at 02:01:00AM +, Keith Smiley wrote:
> From: Keith Smiley
>
> Previously git remote rm did not complete your list of removes as remove
> does.
Your signed-off-by[1] is missing, could you please add that?
[1]:
https://github.com/git/git/blob/master/Documentation/Submitti
On Tue, Jan 16, 2018 at 08:18:14AM +0100, Christian Couder wrote:
> Using a static buffer in sha1_file_name() is error prone
> and the performance improvements it gives are not needed
> in most of the callers.
>
> So let's get rid of this static buffer and, if necessary
> or helpful, let's use one
On Wed, Jan 17, 2018 at 07:44:19AM +0700, Duy Nguyen wrote:
> On Tue, Jan 16, 2018 at 10:57:34AM -0800, Junio C Hamano wrote:
> > Duy Nguyen writes:
> >
> > > On Tue, Jan 16, 2018 at 4:43 AM, Keith Smiley wrote:
> > >> So it sounds like either we should deprecate rm, or I should update the
> >
On Tue, Jan 16, 2018 at 12:48:32PM +0100, Andreas Schwab wrote:
> On Jan 15 2018, Michael Giuffrida wrote:
>
> > It doesn't seem like a useful feature -- you wouldn't expect `git
> > fetch --prune` to remove your local branches that you were developing
> > on, right?
>
> Don't mix local and remo
> -Original Message-
> From: Duy Nguyen [mailto:pclo...@gmail.com]
> Sent: Monday, April 10, 2017 4:24 AM
> To: Kevin Willford
> Cc: git@vger.kernel.org; gits...@pobox.com; p...@peff.net; Kevin Willford
>
> Subject: Re: [PATCH 3/3] reset.c: update files when using s
> -Original Message-
> From: git-ow...@vger.kernel.org [mailto:git-ow...@vger.kernel.org] On
> Behalf Of Duy Nguyen
> Sent: Wednesday, April 12, 2017 7:21 AM
> To: Kevin Willford
> Cc: Kevin Willford ; git@vger.kernel.org;
> gits...@pobox.com; p...@peff.net
>
Hi Jonathan,
I work on the network protocols for the GVFS project at Microsoft.
I shared a couple thoughts and questions below.
Thanks,
Kevin
-Original Message-
From: Stefan Beller [mailto:sbel...@google.com]
Sent: Tuesday, March 28, 2017 7:20 PM
To: Jonathan Tan ; Ben Peart
Cc: git
PATH that lists multiple places in a colon separated list.
https://public-inbox.org/git/CAJF7t-dqSa7tmQqNEWmg_VZ=+832nsz-3jmsga03qk6ay5e...@mail.gmail.com/
Kevin
On Tue, Apr 18, 2017 at 12:48:09PM +, Bonk, Gregory wrote:
>
> I accidently typed 'cd //' and it worked.
>
> gbonk@ICC11167 MINGW64 /c/git/mtb-messagehub-information-radiator (master)
> $ cd //
>
> gbonk@ICC11167 MINGW64 //
> $ cd ..
This has very little to do with git, but more with bash
Hi Jonathan,
Sorry for the delayed response - other work got in the way, unfortunately!
Kevin
-Original Message-
From: Jonathan Tan [mailto:jonathanta...@google.com]
Sent: Thursday, April 13, 2017 4:13 PM
>> I know we're considering server behavior here, but how large do yo
On Sat, Apr 29, 2017 at 12:47:13PM +0200, Robert Eisele wrote:
> Hi,
>
> after having committed folders with lower case naming, I decided to rename
> them to upper-case names. Expecting git to detect them as renamings, it
> started a new parallel hierarchy with new files, which I had to add/commit
On Thu, Apr 27, 2017 at 10:43:16AM +0300, Nikita Orlov wrote:
> Hello, my name is Nikita (male).
>
> Could you explain this (subject) is a bug or a feature?
>
> [snip]
>
> "Some independent changes 1" is missed and its changes are missed as well.
>
> I tried to move another commit to a farther
On Sun, Apr 30, 2017 at 06:47:29PM -0700, Junio C Hamano wrote:
> Kevin Daudt writes:
>
> > Note that git does not store that files are renamed. So a remove + add
> > is the same as a rename in git. Only git status shows it when you for
> > example use git mv directly,
On Tue, May 02, 2017 at 08:52:21PM +0200, Ævar Arnfjörð Bjarmason wrote:
>
> * Due to the bizarro existing semantics of the configure script noted
> upthread if you have a git build script that does --with-libpcre & you
> have libpcre1 installed, it'll link to it, but now since
> --with-libpcre d
uld provide more
details about your problem.
This typically includes what exact command you ran, what the output /
error message you got and any other relevant details.
Kind regards, Kevin.
On Mon, May 15, 2017 at 12:28:58AM +0200, Thomas Schweikle wrote:
> $ git clone
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> linux-stable
> Cloning into 'linux-stable'...
> remote: Counting objects: 5932092, done.
> remote: Compressing objects: 100% (154131/154131), d
On Tue, May 16, 2017 at 09:59:03AM -0700, Eric Rannaud wrote:
> On Tue, May 16, 2017 at 9:18 AM, Jeff King wrote:
> > On Tue, May 16, 2017 at 12:23:02PM +0200, Johannes Schindelin wrote:
> >> It would appear to me that you used a side effect of an implementation
> >> detail: that `git rebase -i` w
On Sun, Apr 22, 2018 at 03:01:10PM -0400, Andrew Wolfe wrote:
> Hi Brian,
>
> Not completely sure what you're saying. If the files on master are
> not changed, the changed files' commit timestamps will be older than
> the branch commit timestamps.
>
> However, if I check out master after committ
s they expected. It turned out
they also had a local file/dir called 'pt', which caused git to checkout
that file/dir rather than creating a local branch based on the remote
branch.
Kevin
is error.
>
> Thanks with Regards,
> Anjali Barodia
Did you remove the hook from the remote repo, or the local repo? Because
this is a hook which runs on the repo you are pushing too. Something
like pre-receive or pre-update is causing this.
Kevin
ve.fsck.zeroPaddedFilemode=ignore=warn (or
> =ignore).
[0]https://public-inbox.org/git/alpine.deb.2.21.1.1801042125430...@minint-6bku6qn.europe.corp.microsoft.com/
Hope this helps, Kevin.
101 - 200 of 494 matches
Mail list logo
