your repository grows over time.
The default isn't just about what's likely to be unique now; it's
about what's likely to stay unique for a period of time.
Hope this helps!
Bryan Turner
On Thu, Jun 30, 2016 at 12:38 PM, Steffen Nurpmeso wrote:
> Hello, for your possible inte
ng such that auto GC
will always be disabled for all repositories and managed explicitly
within Bitbucket Server instead, so a future upgrade should
automatically prevent these messages from appearing on clients.
Best regards,
Bryan Turner
On Fri, Dec 16, 2016 at 9:20 AM, Junio C Hamano wrot
use relative paths in
alternates is something still actively developed and enhanced. Is it
intentional that this breaks the ability to use relative alternates?
If this is to be the "new normal", is there any other option when
using environment variables besides using absolute paths?
Best regards,
Bryan Turner
[1]: https://github.com/git/git/commit/087b6d584062f5b704356286d6445bcc84d686fb
-- Also newly tagged in 2.11.0-rc0
On Mon, Nov 7, 2016 at 4:30 PM, Jeff King wrote:
> On Mon, Nov 07, 2016 at 03:42:35PM -0800, Bryan Turner wrote:
>
>> > @@ -335,7 +340,9 @@ static void link_alt_odb_entries(const char *alt, int
>> > len, int sep,
>> > }
>> >
>&g
>
>> Is there anything I can do to help? I'm happy to test out changes.
>
> The patch at the end of his mail obviously passes the newly-added tests
> for me, but please confirm that it fixes your test suite.
>
> I gather your suite is about noticing behavior changes between different
> versions. Fo
On Tue, Sep 20, 2016 at 9:23 AM, Steffen Nurpmeso wrote:
> Hello again,
>
> yah, sorry, i'm back again..
> I try to find a way to find the name of the current branch in an
> automated way, because i need to ensure that a commit happens on
> it and no other branch. Now the problem arises that the
On Tue, Feb 2, 2016 at 10:28 PM, 孙乾程 wrote:
> I'm not a native English speaker. I'm sorry if I didn't explain the problem
> clearly.
> I'm using Windows 10 Enterprise Insider Preview (I'll use Win10 instead
> below). Until yesterday, I'm using Win10 build 11102, and Git for Windows
> works well
On Fri, Mar 4, 2016 at 9:51 PM, Guilherme wrote:
> Hi,
>
> When doing basic authentication using git clone by passing the
> username and password in the url git clone will first send a GET
> request without the authorization header set.
>
> Am i seeing this right?
I believe this is an intentional
to look at your Stash instance to
determine why authentication is failing. If you do open a support
request, please mention me in your description so that our support
engineers can attach me to the issue!
Best regards,
Bryan Turner
On Wed, Apr 13, 2016 at 12:49 PM, O'Connell, Ken
wrote:
> Good a
On Mon, Dec 10, 2018 at 4:55 PM Owen Ofiesh wrote:
>
> We are seeing an issue where git clone in Linux Ubuntu 14.04.5 LTS fails with
> the following error using the HTTP protocol.
>
> The error on the client is:
>fatal: the remote end hung up unexpectedly
>fatal: early EOF
>fatal: ind
On Fri, Dec 14, 2018 at 10:29 AM Clement Moyroud
wrote:
>
> Hello,
>
> My group at work is migrating a CVS repo to Git. The biggest issue we
> face so far is the performance of git blame, especially compared to
> CVS on the same file. One file especially causes us trouble: it's a
> 30k lines file
On Tue, Apr 2, 2019 at 11:47 PM Amiel Elboim wrote:
> Hi!
>
> I've found strange behavior with 'git describe' command, look like for me as
> bug.
>
> In the case I create 2 tags on same commit and I run 'git describe --tags' I
> expect to get the latest tag, but always I get the first tag I crea
On Wed, Apr 3, 2019 at 1:00 AM Amiel Elboim wrote:
>
> Very helpful! annotated tag is good solution for us.
>
> However fix of this issue is important, because it's confusing when you want
> to track on your version using git tags.
Lightweight tags have no metadata to allow for ordering, so I'm
ng to the
server at all.
I've verified this with Git 2.4.0 as a client (which appears to be
where "git push --atomic" was first introduced), and with Git 2.20.1
as a client, to ensure there wasn't a regression somewhere, and the
behavior is identical for both versions. (I've a
ases, it would likely be quite some time before
that could happen; the minimum supported Git version would need this
series to have landed in or before it. That's a big part of why
Bitbucket Server doesn't use core.hooksPath; it's too new. (Bitbucket
Server 6.0 raised the minimum Git version on the server to 2.11.0, so
it's the first major series that could use core.hooksPath; Bitbucket
Server 5.x supported back to Git 2.2.0, which doesn't have it.)
Best regards,
Bryan Turner
On Fri, Apr 26, 2019 at 11:57 AM David Carson
wrote:
>
> Given that 'ls-remote' can be sorted, it would be useful to be able to ask
> for a subset of the total number of result records.
>
> For example, if I want to retrieve only the tag with the highest version, I
> would do so by adding this n
On Tue, May 14, 2019 at 7:53 AM Cosmin Polifronie wrote:
>
> Hello! I am trying to run 'git worktree add HEAD' in the
> 'pre-commit' hook, more specifically in a Python script that is being
> called from the hook. When doing so, I am greeted with the following
> error:
>
> On Windows 10:
> Prepar
sentially applied the default
behavior--until the default configuration was changed in 1.8.4 from
"never" to "auto". By using "--no-color", even though we didn't "need"
to, we were protected against that change in the default.
Best regards,
Bryan Turner
When using GIT_NAMESPACE, it appears the "symref" added to the
capabilities advertisement doesn't get the namespace stripped. The
namespace is stripped for the advertised refs, including "HEAD", but
not on the "symref".
Lafiel:test bturner$ GIT_NAMESPACE=foo GIT_TRACE_PACKET=1 git ls-remote origin
o about this. It's clear it's a
long-standing behavior. One approach might be to introduce a warning
when changing branches deletes MERGE_*. A different one might be to
fail to change branches without something like --force. I'm not sure
either is _better_ than the current behavior, but
intrinsic metadata of
their own (unlike, say, annotated tags or commits), I suspect
implementing something like this may be more complicated than it might
initially appear, especially if said metadata needs to be communicated
to remote repositories (which implies it might require changes to the
wire prot
27;s tracking
"release/5.16" in my local repository.
I could certainly be misunderstanding the request, but I think it's
asking for something less ephemeral--and more shareable--than
remote-tracking, and it seems logical to want to be able to retain
ancestry while still using remote-tracking setup such that local
branches still track the remote version of themselves, rather than
some other (albeit related) branch.
Best regards,
Bryan Turner
On Tue, Jul 2, 2019 at 10:23 AM Alex Brachet-Mialot
wrote:
>
> Branches behave weirdly for case insensitive filesystems, and I'm
> guessing other things as well. For example say I am on a branch other
> than master, checking out 'Master' will _work_, I will of course be on
> the right branch but g
eds but the code on each "side" isn't entirely compatible,
resulting in broken compilation and/or tests and/or runtime).
Best regards,
Bryan Turner
[1]
https://public-inbox.org/git/CAP4gbxqjHzqHhPuNK8UOwPMa46g2=vcnsk1avgjxn8s+ou-...@mail.gmail.com/
On Tue, Jul 9, 2019 at 4:13 PM Elijah Newren wrote:
>
> Hi John,
>
> On Tue, Jul 9, 2019 at 3:57 PM McRoberts, John wrote:
> >
> > I am responsible for generating a list of all files changed between two
> > successive releases of software. I was using 'git diff' but have run into a
> > problem.
>
On Tue, Jul 16, 2019 at 10:21 AM Junio C Hamano wrote:
>
> Even though we have been sticking to C89, there are a few handy
> features we borrow from more recent C language in our codebase after
> trying them in weather balloons and saw that nobody screamed.
>
> Spell them out.
>
> While at it, ext
.com/git-for-windows/git/releases/tag/v2.23.0-rc0.windows.1
>
> Please test!
I've run the full test suite for Bitbucket Server against 2.23.0-rc0
on Linux, macOS and Windows. No test failures to report.
Thanks again for these early release candidates! They're a great
opportunity to test new releases in advance.
Best regards,
Bryan Turner
On Thu, Aug 1, 2019 at 1:52 PM Alexander Mills
wrote:
>
> Looking for help with this problem:
>
> https://stackoverflow.com/questions/57316783/git-clone-single-branch-does-not-work-for-sha-commit-ids
>
> Essentially looking for:
>
> git clone --single-commit
There's no such option, which will be
omated, so the deprecation warning was not visible.)
For what it's worth, I think having -l mean --list is a _good change_,
and one that will likely be more natural for both new and existing
users. It's the rapid changeover that hurts.
Best regards,
Bryan Turner
[1] https://git-scm.com/docs/git-branch/2.18.0
[2] https://git-scm.com/docs/git-branch/2.19.0
On Wed, Nov 21, 2018 at 6:20 AM Jeff King wrote:
>
> On Tue, Nov 20, 2018 at 03:17:07PM -0800, Bryan Turner wrote:
>
> > I've run 2.20.0-rc0 through the test matrix for Bitbucket Server on
> > both Linux and Windows, and the only failures were related to this
> >
Something of an odd question, but is there something I can do in the
configuration for a repository that forces any "git gc" run in that
repository to always fail without doing anything? (Ideally I'd like to
make "git reflog expire" _also_ fail.)
Background: For Bitbucket Server, we have a fairly
On Tue, Nov 27, 2018 at 3:47 PM Ævar Arnfjörð Bjarmason
wrote:
>
>
> On Tue, Nov 27 2018, Bryan Turner wrote:
>
> >
> > Is there anything I can set, perhaps some invalid configuration
> > option/value, that will make "git gc" (most important) and "git
On Tue, Nov 27, 2018 at 5:55 PM Elijah Newren wrote:
>
> On Tue, Nov 27, 2018 at 4:16 PM Ævar Arnfjörð Bjarmason
> wrote:
> >
> > On Wed, Nov 28 2018, Bryan Turner wrote:
> >
> > > On Tue, Nov 27, 2018 at 3:47 PM Ævar Arnfjörð Bjarmason
> > > wr
On Wed, Nov 28, 2018 at 5:19 PM Junio C Hamano wrote:
>
> > Another issue with the canned steps for "git gc" is that it means it
> > can't be used to do specific types of cleanup on a different schedule
> > from others. For example, we use "git pack-refs" directly to
> > frequently pack the refs i
On Fri, Nov 30, 2018 at 5:05 PM Farhan Khan wrote:
>
> Hi all,
>
> I am writing an implementation of the git HTTP pack protocol in C. It
> just does a request to clone a repository. It works pretty well for
> small repositories, but seems to fail on larger repositories and I do
> not understand wh
On Fri, Nov 30, 2018 at 6:58 PM Bryan Turner wrote:
>
> Here's a (very ugly) patch I threw together on top of your code:
...snip
Gmail butchered my patch, so here it is as an attachment.
Bryan
short-size-reads.patch
Description: Binary data
On Thu, Dec 6, 2018 at 10:49 PM biswaranjan panda
wrote:
>
> I have the following scenario:
>
> On a branch A, I deleted a file foo.txt and committed the change. Then
> I did a bunch of other changes.
> Now I want to undelete foo.txt.
>
> One way is to checkout a separate branch B where the file i
On Thu, Dec 6, 2018 at 11:26 PM Jeff King wrote:
>
> On Thu, Dec 06, 2018 at 11:07:00PM -0800, biswaranjan panda wrote:
>
> > Thanks! Strangely git log --follow does work.
>
> I suspect it would work even without --follow. When you limit a log
> traversal with a pathspec, like:
>
> git log foo
>
On Sun, Sep 9, 2018 at 6:31 AM Dylan Young wrote:
>
> Works:
>
> git show -C --find-copies-harder 055f6c89fa4506037d1621761f13430f469b8029
>
> git show -C --find-copies-harder
> 055f6c89fa4506037d1621761f13430f469b8029 --name-status
Here, because you didn't provide _any_ paths, Git is allowed to
On Wed, Oct 3, 2018 at 12:34 PM Dimitri Kopriwa wrote:
>
> I have replaced the way I fill the git credentials store, I have verify
> ~/.git-credentials and information are there, the ~/.gitconfig look fine
> too.
>
> I still have 401 error when reading from that file.
>
> This is the paste log : h
On Tue, Jun 5, 2018 at 2:33 PM Heinz, Steve wrote:
>
> Hi.
>
> I am new to Git and have read quite a few articles on it.
> I am planning on setting up a remote repository on a windows 2012 R2 server
> and will access it via HTTPS.
> I am setting up a local repository on my desk top (others in my
On Fri, Jun 22, 2018 at 1:45 PM Marc Strapetz wrote:
>
> On 22.06.2018 19:36, Johannes Sixt wrote:
> > Am 22.06.2018 um 14:04 schrieb Marc Strapetz:
> >> On Windows, when creating following repository:
> >>
> >> $ git init
> >> $ echo "1" > file.txt
> >> $ git add .
> >> $ git commit -m "initial i
On Mon, Jun 25, 2018 at 9:34 AM Junio C Hamano wrote:
>
> Bryan Turner writes:
>
> > Git on Windows is not designed to run with anything other than
> > core.ignoreCase=true, and attempting to do so will cause unexpected
> > behavior.
>
> Even though I fully ag
'm not looking for anything to change here, let me hasten to add; I'm
just interested in some clarification. Why did our invalid ref
advertisement response work in older Git versions? Why has it stopped
working in 2.21?
Best regards,
Bryan Turner
On Tue, Mar 12, 2019 at 10:23 AM 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 commit due to
On Tue, Mar 12, 2019 at 11:01 AM Robert P. J. Day wrote:
>
> On Tue, 12 Mar 2019, Bryan Turner wrote:
>
> > On Tue, Mar 12, 2019 at 10:23 AM Robert P. J. Day
> > wrote:
> > >
> > > never noticed this before ... when i do a regular "git commit"
On Tue, Mar 12, 2019 at 11:14 AM Robert P. J. Day wrote:
>
> On Tue, 12 Mar 2019, Bryan Turner wrote:
>
> > On Tue, Mar 12, 2019 at 10:23 AM Robert P. J. Day
> > wrote:
> > >
> > > never noticed this before ... when i do a regular "git commit"
On Thu, Mar 21, 2019 at 9:59 AM Robert Dailey wrote:
>
> I have a particular tag in my repo that shows 2 annotated
> descriptions, which is very confusing.
>
> The command I ran:
>
> ```
> git show --format=fuller 4.2.0.1900
> ```
>
> And the output:
>
> ```
> tag 4.2.0/1900
> Tagger: John Doe
On Mon, Mar 25, 2019 at 7:49 AM Jeff King wrote:
>
> On Mon, Mar 25, 2019 at 08:50:14AM -0500, Robert Dailey wrote:
>
> > On Thu, Mar 21, 2019 at 2:29 PM Jeff King wrote:
> > > Tags can point to any object, including another tag. It looks like
> > > somebody made an annotated tag of an annotated
I'm trying to assist a Bitbucket Server customer who is seeing some
"git-upload-pack" processes "hang" on their server.
While investigating, we had them connect gdb to their processes (which
are 2.10.0 built from source using a simple unzip-and-run-make
approach) and get the backtraces for them. T
On Wed, Mar 27, 2019 at 6:50 PM Jeff King wrote:
>
> On Wed, Mar 27, 2019 at 05:49:27PM -0700, Bryan Turner wrote:
>
> > I'm trying to assist a Bitbucket Server customer who is seeing some
> > "git-upload-pack" processes "hang" on their server.
> &
On Wed, Aug 15, 2018 at 1:50 PM Hadi Safari wrote:
>
> Hi everyone!
>
> I encountered a strange situation on OS X recently. I cloned a
> repository (https://github.com/kevinxucs/Sublime-Gitignore.git), went to
> folder, and saw "Changes not staged for commit" message for four
> specific files. It
time, they make a
big difference in my day to day work. And that's not to mention all
the Bitbucket Server and Bitbucket Data Center users who will enjoy a
snappier experience as these changes make their way out into the wild.
Best regards,
Bryan Turner
the issue
Everything here is working as intended. If you want to push to a
_remote_, you either need to:
- Name the remote ("git push origin"), or
- Leave it off, so Git will assume origin ("git push")
Pushing to a URL that matches a remote's URL is _not_ pushing to a
remote. It's pushing to an explicit URL.
Hope this helps,
Bryan Turner
>
>
>
On Thu, Aug 8, 2019 at 2:08 PM wrote:
>
> fwiw,
>
> jimc@frodo:~/prj-1/capnproto.git$ git branch -l
> * master
>
> I find the splat in the response unhelpful
> when wrapped in shell for loop, the splat expands into everything in
> current directory
>
> jimc@frodo:~/prj-1/capnproto.git$ for b in `g
he tagged
tag's SHA.
Is there any way, with "git for-each-ref", to output the "fully"
peeled SHA of a tag's ultimate target, regardless of how many layers
must be traversed?
Best regards,
Bryan Turner
On Mon, Aug 19, 2019 at 10:50 PM Junio C Hamano wrote:
>
> Bryan Turner writes:
>
> > Is there any way, with "git for-each-ref", to output the "fully"
> > peeled SHA of a tag's ultimate target, regardless of how many layers
> > must be tr
cented "e", wouldn't it be better to set your
name using é, rather than a trailing apostrophe? "git commit" would
likely preserve that without issue.
Best regards,
Bryan Turner
On Fri, Aug 23, 2019 at 6:59 PM wrote:
>
> Hi All,
>
> I'm trying to answer a question for a customer on clone performance. They
> are doing at least 2-3 clones a day, of repositories with about 2500 files
> and 10Gb of content. This is stressing the file system.
Can you go into a bit more detail
On Tue, Aug 27, 2019 at 2:32 PM Uwe Kleine-König
wrote:
>
> On Tue, Aug 27, 2019 at 02:59:30PM -0400, Jeff King wrote:
> > On Tue, Aug 27, 2019 at 12:04:27PM +0200, Uwe Kleine-König wrote:
> >
> > to see the loose ones. If there are a lot, try:
> >
> > git pack-refs --prune --all
> >
> > (or jus
indicated you have "diff.renames=copies", wouldn't you need
-C? -M only detects renames, not copies.
(I haven't looked too deeply into the rest, but this detail caught my eye.)
Best regards,
Bryan Turner
> 3. The `diff.renames` config doesn't seem to be working here, when it s
On Fri, Mar 16, 2018 at 2:01 PM, Briggs, John wrote:
> No, it was a fresh install. Plus file search reveals only one copy of the
> file.
>
> I also noticed that I cannot use the file properties to run as administrator.
> I must right-click on Git GUI and select "More >> Run as administrator" in
On Fri, Mar 23, 2018 at 10:47 AM, Johannes Schindelin
wrote:
> Hi team,
>
> On Wed, 21 Mar 2018, Junio C Hamano wrote:
>
>> A release candidate Git v2.17.0-rc1 is now available for testing
>> at the usual places. It is comprised of 493 non-merge commits
>> since v2.16.0, contributed by 62 people,
On Thu, Apr 5, 2018 at 12:42 PM, Thierry Moreau
wrote:
> Dear GIT enthusiasts!
>
> This ends up with a "git checkout" command aborting. A bit frustrating at
> the early stage of GIT learning curve.
>
> My first goal is to clone repositories locally in order to explore the
> various linux kernel ve
On Thu, Apr 5, 2018 at 4:18 PM, Bryan Turner wrote:
> On Thu, Apr 5, 2018 at 12:42 PM, Thierry Moreau
> wrote:
>> Dear GIT enthusiasts!
>>
>> This ends up with a "git checkout" command aborting. A bit frustrating at
>> the early stage of GIT learnin
> proposed change would introduce unseen issues.
>
>
> Thanks,
> Satya
Hope this helps!
Bryan Turner
sh" (or
something other than "auto") to avoid the automatic detection.
I'd love to say I have a brilliant idea for how to work around this,
oh and here's a patch, but I don't. One option might be trying to
actually review the output, and another might be to run "ssh -V", but
both of those have their own flaws (and the extra process forks aren't
"free").
[1] https://www.openssh.com/txt/release-6.8
[2] https://launchpad.net/ubuntu/+source/openssh
Best regards,
Bryan Turner
On Tue, Jan 2, 2018 at 9:07 PM, Jonathan Nieder wrote:
> Hi Bryan,
>
> Bryan Turner wrote:
>
>> Our test environment is still on Ubuntu 12.04 LTS (it's a long story,
>> but one I doubt is unique to us), which means it's using OpenSSH 5.9.
>> ssh -G was ad
d that
commit is fast-forward from the target, a new commit is not created
and instead the target branch is fast-forwarded. With "--no-ff", it's
questionable what "--squash" should do in that case. Fast-forward
anyway? Rewrite the commit simply to get new committer details and
SHA-1?
Hope this helps!
Bryan Turner
On Fri, Jan 5, 2018 at 12:35 PM, Robert Dailey wrote:
> On Fri, Jan 5, 2018 at 2:26 PM, Paul Smith wrote:
>> On Fri, 2018-01-05 at 12:12 -0800, Bryan Turner wrote:
>>> On Fri, Jan 5, 2018 at 11:59 AM, Robert Dailey
>>> wrote:
>>>
>>> As for why t
On Tue, May 2, 2017 at 6:33 PM, Paul van Wichen
wrote:
> Hi,
>
> We are having a strange issue that we haven't been able to pin down.
> Scenario: master branch and feature branch both have a specific file.
> 1. Master checked out.
> 2. git status show no changes / clean staging area.
> 3. Checkout
r log, to review
them. If they don't meet your requirements, just reject the push and
Git will delete the objects automatically
Hope this helps!
Bryan Turner
>
> Thanks in advance,
> Ákos Tajti
>
[1]: https://git-scm.com/docs/githooks includes documentation for
pre-receive inpu
Andrew,
On Thu, Apr 19, 2018 at 6:55 AM, Andrew Ducker
wrote:
>
> What happens:
> When I create a new tag on the remote (changing nothing else)
> "git pull origin master" produces the following:
> From git.internal.company.com:team/testrepo
>* branchmaster -> FETCH_HEAD
>
On Fri, Apr 27, 2018 at 12:08 PM, Wink Saville wrote:
>
> The other change was rather than using
> ""+refs/tags/*:refs/remote-tags/$name/*"
> I've changed it to "+refs/tags/*:refs/remote/tags/$name/*" which seems
> cleaner.
> Again, if remote-tags is preferred I'll change it back.
>From lookin
On Wed, May 9, 2018 at 3:09 PM Randall S. Becker
wrote:
> The question: what is the best practice for versioning the parts of
> clean/smudge filters that are in .git/config given that only some users in
> my environment will be cloning the repository in question and that I
really
> can't put the
ms and on NTFS on Windows.
Hope this helps!
Bryan Turner
> $ GIT_TRACE=1 git commit --allow-empty -v -m "lol"
> 11:37:24.594795 git.c:369 trace: built-in: git 'commit'
> '--allow-empty' '-v' '-m' 'lol'
> 11:37:24.605842 run-command.c:369 trace: run_command: 'gpg'
> '--status-fd=2' '-bsau' '8AEC0DB537A9FC7E'
> error: gpg failed to sign
I'm one of the Bitbucket Server developers. My apologies; I just
noticed this thread or I would have jumped in sooner!
On Thu, Jul 6, 2017 at 6:31 AM, Andreas Krey wrote:
> On Wed, 05 Jul 2017 04:20:27 +, Jeff King wrote:
>> On Tue, Jul 04, 2017 at 09:57:58AM +0200, Andreas Krey wrote:
> ...
On Thu, Jul 6, 2017 at 10:23 AM, Kyle Meyer wrote:
> Junio C Hamano writes:
>> Kyle Meyer writes:
>
>> What is the answer desired by your application when two or more
>> branches point at the same commit you are interested in? Pick one at
>> random? An error saying it cannot decide where to pl
On Mon, Jul 10, 2017 at 9:45 PM, Andreas Krey wrote:
> On Thu, 06 Jul 2017 10:01:05 +0000, Bryan Turner wrote:
>
>> I also want to add that Bitbucket Server 5.x includes totally
>> rewritten GC handling. 5.0.x automatically disables auto GC in all
>> repositories a
On Wed, Jan 24, 2018 at 3:55 PM, Mark Waite wrote:
> It appears that git 2.16.0 and 2.16.1 have introduced a change which
> surprises the Jenkins git client plugin.
>
> Git 2.16.0 and 2.16.1 on Linux both report "fatal: ssh variant
> 'simple' does not support setting port" when used in the context
On Mon, Jan 29, 2018 at 11:08 AM, H wrote:
> I am a newcomer to git looking to set up a web development environment where
> individual computers are used for development, the development.git,
> staging.git and production.git repositories are stored on an external server
> reachable by password-
ormal" (albeit
rare) case? Or could it represent some sort of issue in Git's 3-way
merge algorithm (in its behavior or perhaps in how the merge conflicts
are logged)?
Any insights appreciated!
Bryan Turner
On Tue, Feb 6, 2018 at 1:41 AM, Zsolt SZALAI wrote:
> Hi,
>
> I wonder if there is a feature with which the history of the
> repository can be listed?
> i am interested in especially the usecases of pull and push, i.e. to
> query when the a branch was refreshed with remote changes and which
> comm
On Fri, Feb 16, 2018 at 3:30 PM, Johannes Schindelin
wrote:
> Hi team,
>
> I am unwilling to release Git for Windows v2.16.2 on a Friday night, but I
> have something almost as good. There is a snapshot available here:
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wingit.blob
On Mon, Feb 27, 2017 at 6:27 PM, G. Sylvie Davies
wrote:
> Is there any appetite for base64'd commit-id's, using the url-safe
> variant (e.g. RFC 4648 [1] with padding removed)?
>
> And so this:
> 712bad335dfa9c410a83f9873614a19726acb3a8
>
> Becomes this:
> cSutM136nEEKg_mHNhShlyass6g
>
>
> Under
is: why not implementing some feature, that would
> somehow handle this problem?
Like Git LFS or git annex? Features have been implemented to better
handle large files; they're just not necessarily part of core Git.
Have you checked whether one of those solutions might work for your
use case?
Best regards,
Bryan Turner
al Git list isn't interested in this issue.)
Best regards,
Bryan Turner
itly, to be certain, but just based on reading the
overview and knowing our code I think the described approaches should
work fine.
Best regards,
Bryan Turner
On Thu, Aug 24, 2017 at 3:53 PM, Brandon Williams wrote:
> +
> + version = getenv("GIT_PROTOCOL");
> + if (!strcmp(version, "2"))
> + upload_pack_v2();
> +
I think the "if" check here needs some type of NULL check for
"version" before calling "strcmp". Without that, if t
On Wed, Aug 30, 2017 at 2:12 PM, Brandon Williams wrote:
> On 08/30, Bryan Turner wrote:
>> On Fri, Aug 25, 2017 at 10:29 AM, Jeff King wrote:
>> > On Thu, Aug 24, 2017 at 03:53:21PM -0700, Brandon Williams wrote:
>> >
>> >> The biggest question I'm
On Tue, Sep 5, 2017 at 5:53 PM, Daniel Biran wrote:
>
>>> I'm trying to better understand one of the merge algorithms as I had some
>>> triumphs and tribulations with using a set of commands during a merge.
>>> tldr: can a git merge -s recursive -X patience; // result in a fast-forward
>>> merg
ugh. In general, `git
blame` and `git diff`, for example, don't seem honor them. Perhaps
someone else knows of some useful knows of which I'm not aware.
Best regards,
Bryan Turner
as a canary (pending the final 2.15.0
release). I've done the same for 2.15.0-rc2 on Linux as well.
Best regards,
Bryan Turner
On Thu, Oct 26, 2017 at 2:07 AM, Jacob Keller wrote:
> On Wed, Oct 25, 2017 at 10:38 PM, Junio C Hamano wrote:
>> Johannes Schindelin writes:
>>
>>> Note that the correct blib path starts with `C:\BuildAgent\_work` and
>>> the line
>>>
>>> use lib (split(/:/, $ENV{GITPERLLIB}));
>>>
>>> sp
On Thu, Oct 26, 2017 at 2:07 AM, Jacob Keller wrote:
> On Wed, Oct 25, 2017 at 10:38 PM, Junio C Hamano wrote:
>> Johannes Schindelin writes:
>>
>>> Note that the correct blib path starts with `C:\BuildAgent\_work` and
>>> the line
>>>
>>> use lib (split(/:/, $ENV{GITPERLLIB}));
>>>
>>> sp
On Tue, Nov 14, 2017 at 1:18 AM, Robert P. J. Day wrote:
>
> just noticed something i was unaware of -- some git commands can't
> be run if i'm in the .git directory, while others can. for example,
> if i "cd .git", commands like this work just fine:
>
> $ git show
> $ git branch
> $ git l
57ac1
Author: Ronnie Sahlberg
Date: Wed Apr 30 09:22:45 2014 -0700
refs.c: make delete_ref use a transaction
Best regards,
Bryan Turner
--
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
bisect good
d3038d22f91aad9620bd8e6fc43fc67c16219738 is the first bad commit
commit d3038d22f91aad9620bd8e6fc43fc67c16219738
Author: Jeff King
Date: Wed Oct 15 18:41:35 2014 -0400
prune: keep objects reachable from recent objects
Best regards,
Bryan Turner
--
To unsubscribe from this list: send th
On Mon, Nov 10, 2014 at 8:22 PM, Jeff King wrote:
> On Mon, Nov 10, 2014 at 07:47:32PM +1100, Bryan Turner wrote:
>
>> First change: git update-ref -d /refs/heads/nonexistent
>> now produces an error about ref locking that it
>> didn't produce before
>>
&
1 - 100 of 130 matches
Mail list logo
