To whom this may concern,
I found a bug in git while trying to push my website.
I redid the process and it happened again.
I also tried it on another computer and it happened again.
I was wondering how to claim a bug?
Thank you,
Michael Hawes
icenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-cygwin".
Type "show configuration&
bug to me !
Regards,
Aaron
--
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
Am 1/14/2013 10:18, schrieb Nikolay Frantsev:
> nikolay@localhost:~/Desktop/git-stash_bug/bug$ git status
> # On branch master
> # Changes to be committed:
> # (use "git reset HEAD ..." to unstage)
> #
> # new file: 3
> #
> # Changes not staged for c
, destination=lib/Logger.h
It looks and smells like a bug to me !
Not really. When you attempt to overwrite an existing file with 'git
mv', you get this error message on both Windows and Linux.
The difference is that logger.h and Logger.h are the same file on
Windows, but they are not on Li
I do a :-
>>
>> git mv logger.h Logger.h
>>
>> I get the following :-
>>
>> fatal: destination exists, source=lib/logger.h,
>> destination=lib/Logger.h
>>
>> It looks and smells like a bug to me !
>
>
> Not really. When you attempt
On 31 January 2016 at 15:05, Doug Kelly wrote:
> On Sun, Jan 31, 2016 at 8:50 AM, Johannes Sixt wrote:
>> Am 31.01.2016 um 15:03 schrieb Aaron Gray:
>>> I think I have found a possible difference in behaviour between
>>> Windows git commandline distro and Linux git
>>>
>>> basically If I do a :-
-
>>
>> git mv logger.h Logger.h
>>
>> I get the following :-
>>
>> fatal: destination exists, source=lib/logger.h,
>> destination=lib/Logger.h
>>
>> It looks and smells like a bug to me !
>
>
> Not really. When you attempt
atal: destination exists, source=lib/logger.h, destination=lib/Logger.h
>
> It looks and smells like a bug to me !
Which version of Git are you using ?
Because it is fixed in the latest version in Git and Git for Windows.
--
To unsubscribe from this list: send the line "unsu
>
> > git mv logger.h Logger.h
> >
> > I get the following :-
> >
> > fatal: destination exists, source=lib/logger.h, destination=lib/Logger.h
> >
> > It looks and smells like a bug to me !
Thanks for your bug report. Having said that, I would l
I have a file
app/Controller/CustomerCardVerificationController.php
And when I take a look at changes log, I get this (no matter which tool
I use):
2017-07-31 19:41 dule o membership renew payment email
2017-06-07 08:59 Dusan Tatic o cc refund clean
2017-04-15 00:16 Miodrag
Though it might not be considered a bug 'per se' it is definitely wired.
Namely, when you type 'yes' word and hit enter in git bash for widnows,
the process enters infinite loop and just prints 'y' letter in new line.
It can be interrupted with CTRL+C. I&
I think I have identified an obscure bug. I have a reproducible test case.
I am trying to come up with enough of a test case that can be used for
finding and fixing the issue.
I have a set of patches. They are diffs. Some have whitespace issues.
(Which I believe triggers the bug.)
The patches go
Hi, Michael.
It would be helpful to get more context on what triggered this bug. I'm
not a 'core' dev, so there may be a better way to send this. In general,
you want to state the following:
0) Information about your git installation, host system, etc.
1) Information about yo
On Tue, 2016-09-13 at 13:18 -0400, Mike Hawes wrote:
> To whom this may concern,
>
> I found a bug in git while trying to push my website.
> I redid the process and it happened again.
> I also tried it on another computer and it happened again.
> I was wondering how to claim a bu
Hello,
I couldn’t find any documentation on submitting patches for gitk.
I saw in Documentation/SubmittingPatches that gitk is maintained in
its own repo.
I can’t clone repo’s unless they’re http while on my corporate proxy.
I’m hoping someone can help me out or just do it for me ;-)
I’d like to r
Ilya Tumaykin gmail.com> writes:
> $ git --no-pager log -1 --format='format:%+s%+b'
> Please fix.
Simply use `git --no-pager log -1 --format='format:%+s%n%+b'`
The message body excludes the empty line preceding it.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the bo
Today, I managed to create a duplicate branch in a git repository. While
this may not be a bug per se, I do think that it is confusing and some way
of preventing such issues in the future may be helpful.
I first cloned the repository:
$ git clone https://github.com/CodeForChicago/superclass.git
Hi all,
Yestoday when I worked using Git, I found a bug. It's about
rebase. Or I don't know if it is a bug, maybe that is Git. Below is my
problem:
There is a master branch, and we develop in our own branch.
Let's simplify this: there are two branches created at the sa
Hello.
I have found a bug in opentracker // http://erdgeist.org/gitweb/opentracker/
, or it is something wrong with my PC (?).
Every time when I access statistics page at
"localhost:6969/st?mode=everything", it redirects my browser to
"http://www.localhost.com:6969/st?mode=e
Hello.
I have found a bug in opentracker // http://erdgeist.org/gitweb/opentracker/ ,
or it is something wrong with my PC (?).
Every time when I access statistics page at
"localhost:6969/st?mode=everything", it redirects my browser to
"http://www.localhost.com:6969/st?mode=e
Hi all!
I just ran into a problem that I'm pretty sure is a bug in git. Just
read and run this (fairly trivial) shell script to replicate.
Thanks!
---John Whitney
git_failure.sh
Description: Bourne shell script
There's a problem using git with files having cyrillic 'й' in their name, git
just can't track them.
uname: Darwin 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT
2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
git version: 1.7.12.1 (from macports)
Steps to reproduce:
- git init
and the target system doesn't
happen to be recent glibc.
I'm not sure where to pin the bug exactly — on fetch-pack.c, on
git-compat-util.h, on configure for not seeing if one of those fields
actually exists and setting NO_NSEC otherwise, or elsewhere, but I
would be tempted to fix it
Hi,
In imap-send.c:socket_perror() we pass |func| as a parameter, which I
think it is the name of the function that "called" socket_perror, or
the name of the function which generated an error.
But at line 184 and 187 it always assume it was SSL_connect.
Should we instead call perror() and ssl_s
Hello,
I have faced a git bug. When I try to clone a git repo it
shows an error "protocol error: bad pack header".
This is the full error message which I got while cloning git
project :
Clone: protocol error: bad pack header
$ git clone -v --prog
Hi All,
My system: RedHat 6.5/64-bit (gcc 4.4.7)
My configuration options: ./configure --prefix=/home/albert/soft
Compilation of git 2.2.2 itself was fine, but some tests failed.
I presume, there might be some network communication restrictions here in
the lab
(gitweb had f
Hey Guys,
I am Abhishek, I am new here.
For now I just have one question is there any centralize DB place where
I can see Bugs reported on / about Git ? something like bugzilla of trac for
Git-Scm ?
--
Thanks
Abhishek
http://thezeroth.net
--
To unsubscribe from this list: send the line "unsub
On Thu, Feb 6, 2014 at 7:01 AM, Junio C Hamano wrote:
>
> The latest maintenance release Git v1.8.5.4 is now available at
> the usual places.
>
I have an git repo PROJECT.git, the full path is /srv/repo/git/PROJECT.git,
when I set git_base_url_list in gitweb.conf:
@git_base_url_list = qw(https:/
According to the gitattributes docs:
"When more than one pattern matches the path, a later line overrides
an earlier line. This overriding is done per attribute."
I had a need to do this recently, and while the attributes are git-lfs
specific, I think the issue may be generic.
Summary: Trying to
Hi everyone,
I released today git-bug, a distributed bug tracker that embeds in
git. It use git's internal storage to store bugs information in a way
that can be merged without conflict. You can push/pull to the normal
git remote you are already using to interact with other people. Normal
sibling directories (see test case),
the new logic would accidentally send that object as an extra.
However, I found a bug in the existing logic. The included test
demonstrates this during the final 'git index-pack' call. It
fails with the message
'fatal: pack has 1 unresolv
Converting to BUG() makes it easier to detect and debug
cases where we hit this assertion. Coupled with a new test
in t1300, this shows that the test suite can detect such
corner cases.
Signed-off-by: Jeff King
---
environment.c | 2 +-
t/t1300-repo-config.sh | 6 ++
2 files
On Mon, Mar 19, 2018 at 09:49:28PM -0400, Dakota Hawkins wrote:
> Summary: Trying to apply attributes to file extensions everywhere
> except in one directory.
>
> .gitattributes:
>
> *.[Pp][Nn][Gg] filter=lfs diff=lfs merge=lfs -text
> /.readme-docs/ -filter=lfs -diff=lfs -merge=lfs
>
>
Thanks for the quick reply!
On Mon, Mar 19, 2018 at 10:34 PM, Jeff King wrote:
> On Mon, Mar 19, 2018 at 09:49:28PM -0400, Dakota Hawkins wrote:
>
>> Summary: Trying to apply attributes to file extensions everywhere
>> except in one directory.
>>
>> .gitattributes:
>>
>> *.[Pp][Nn][Gg] filter
Sorry to tack on to my previous email, but I just thought of this:
If something like "-diff=lfs" won't do what I (and git-lfs) thought it
would, do you think it would be prudent/reasonable to suggest git-lfs
add a "no-lfs" filter for exactly this case? That way I could have
explicit exclusions wit
Jeff King writes:
> The best you can probably do is:
>
> /.readme-docs/* diff=foo
>
> Since you have no diff.foo.* config, that will behave in the default way
> (including respecting the usual "is it binary" checks). So a bit hacky,
> but I think it would work as "ignore prior diff".
You can s
On Mon, Mar 19, 2018 at 11:33 PM, Junio C Hamano wrote:
> Jeff King writes:
>
>> The best you can probably do is:
>>
>> /.readme-docs/* diff=foo
>>
>> Since you have no diff.foo.* config, that will behave in the default way
>> (including respecting the usual "is it binary" checks). So a bit hac
On Mon, Mar 19, 2018 at 08:33:15PM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > The best you can probably do is:
> >
> > /.readme-docs/* diff=foo
> >
> > Since you have no diff.foo.* config, that will behave in the default way
> > (including respecting the usual "is it binary" checks
On Mon, Mar 19, 2018 at 11:10:26PM -0400, Dakota Hawkins wrote:
> > As you noted below, that second line does not match your path, because
> > attributes on a directory aren't applied recursively. And it has nothing
> > to do with overriding. If you remove the png line entirely, you can see
> > th
On Mon, Mar 19, 2018 at 11:17:04PM -0400, Dakota Hawkins wrote:
> Sorry to tack on to my previous email, but I just thought of this:
>
> If something like "-diff=lfs" won't do what I (and git-lfs) thought it
> would, do you think it would be prudent/reasonable to suggest git-lfs
> add a "no-lfs"
> Right. The technical reason is mostly "that is not how it was designed,
> and it would possibly break some corner cases if we switched it now".
I'm just spitballing here, but do you guys think there's any subset of
the combined .gitignore and .gitattributes matching functionality that
could at l
On Tue, Mar 20, 2018 at 12:25:27AM -0400, Dakota Hawkins wrote:
> > Right. The technical reason is mostly "that is not how it was designed,
> > and it would possibly break some corner cases if we switched it now".
>
> I'm just spitballing here, but do you guys think there's any subset of
> the co
> So I think the "recommended subset" is basically "everything but these
> few constructs". We just need to document them. ;)
Mentioned so-far/running list?
- Matching directories recursively, or at all I guess (e.g. "/")
- (???) Instead: "/*"
- Negative matches
- (???) Instead: Is there any
On Tue, Mar 20, 2018 at 5:40 AM, Jeff King wrote:
> On Tue, Mar 20, 2018 at 12:25:27AM -0400, Dakota Hawkins wrote:
>
>> > Right. The technical reason is mostly "that is not how it was designed,
>> > and it would possibly break some corner cases if we switched it now".
>>
>> I'm just spitballing h
Thinking about this a little more, I'm now attracted to the idea that
its .gitignore that's weird.
As I understand it, .gitignore stops recursion when there's a
directory match (`somedir/`) but also explicitly allows nested
.gitnore file _as well as_ exclusion (`!*.txt`).
So, in the following (co
On Tue, Mar 20, 2018 at 11:22:02PM -0400, Dakota Hawkins wrote:
> Thinking about this a little more, I'm now attracted to the idea that
> its .gitignore that's weird.
>
> As I understand it, .gitignore stops recursion when there's a
> directory match (`somedir/`) but also explicitly allows nested
> I think that ignoring all of /ignore-most/ is much more efficient, since
> we don't have to enumerate the paths inside it at all (which is why the
> current behavior works as it does).
That's definitely true, but I wonder what the impact would be for most
cases (even for most cases with large re
One extra note:
I was burned by this just a few hours ago in a new repo (but because
of this discussion I realized what the problem was pretty quickly).
In the top-level .gitignore I had
build/
...
!alpine/build/
where `build/` was a stock ignore line among hundreds that I blindly
p
On Wed, Mar 21, 2018 at 03:36:09AM -0400, Dakota Hawkins wrote:
> > I think that ignoring all of /ignore-most/ is much more efficient, since
> > we don't have to enumerate the paths inside it at all (which is why the
> > current behavior works as it does).
>
> That's definitely true, but I wonder
> I think it means "for the rest of the description of how the patterns
> work". I.e., "foo/" matches as "foo" when the rest of the matching rules
> are applied. I agree it's a bit awkward. Patches welcome. :)
I'd be more than happy to do that!
It will take me a while, this (email and text-patche
On Wed, Mar 21, 2018 at 04:35:26AM -0400, Dakota Hawkins wrote:
> > I think it means "for the rest of the description of how the patterns
> > work". I.e., "foo/" matches as "foo" when the rest of the matching rules
> > are applied. I agree it's a bit awkward. Patches welcome. :)
>
> I'd be more t
On Wed, Mar 21, 2018 at 4:22 AM, Dakota Hawkins
wrote:
> Thinking about this a little more, I'm now attracted to the idea that
> its .gitignore that's weird.
>
> As I understand it, .gitignore stops recursion when there's a
> directory match (`somedir/`) but also explicitly allows nested
> .gitnor
Dakota Hawkins writes:
> At any rate, would it at least be a good idea to make the "trailing
> slash halts recursion, won't consider nested .gitignore files"
> explicit in the `.gitignore` doc? Unless I'm missing it, I don't think
> that behavior is called out (or at least not called out concisel
I really like this idea. I've often wanted an integrated bug database like
this. My solution has always been to have a subrepo storing bug reports and
coments in .txt files and then using bash porcelain scripts to make a git-like
interface. I think I like this better. My only nit is Go.
Hi,
Michael Muré wrote:
> I released today git-bug, a distributed bug tracker that embeds in
> git. It use git's internal storage to store bugs information in a way
> that can be merged without conflict. You can push/pull to the normal
> git remote you are already using to in
On Sat, Aug 18 2018, Jonathan Nieder wrote:
> Hi,
>
> Michael Muré wrote:
>
>> I released today git-bug, a distributed bug tracker that embeds in
>> git. It use git's internal storage to store bugs information in a way
>> that can be merged without confli
Michael Muré writes:
> I released today git-bug, a distributed bug tracker that embeds in
> git. It use git's internal storage to store bugs information in a way
> that can be merged without conflict. You can push/pull to the normal
> git remote you are already using to in
Hi,
Ævar Arnfjörð Bjarmason wrote:
> On Sat, Aug 18 2018, Jonathan Nieder wrote:
>> Michael Muré wrote:
>>> I released today git-bug, a distributed bug tracker
[...]
>> I am a bit unhappy about the namespace grab. Not for trademark
>> reasons: the Git trademark rul
On Sat, Aug 18 2018, Jonathan Nieder wrote:
> Hi,
>
> Ævar Arnfjörð Bjarmason wrote:
>> On Sat, Aug 18 2018, Jonathan Nieder wrote:
>>> Michael Muré wrote:
>
>>>> I released today git-bug, a distributed bug tracker
> [...]
>>> I am a bit u
the API of seamlessly integrating 3rd party tools.
I think we're talking past each other. I haven't proposed any blanket
policy. I'm saying that "git bug" is a bad name for this tool:
- it's hard to find with search engines
- it conflicts with some likely good f
me now" without considering how widely used it is. It's us who
>> decided to expose the API of seamlessly integrating 3rd party tools.
>
> I think we're talking past each other. I haven't proposed any blanket
> policy. I'm saying that "git bug" is
Ævar Arnfjörð Bjarmason wrote:
> I'm just pointing out in the more general case that if someone comes up
> with a badly named git-xyz it doesn't scale to try to point this out to
> them before git-xyz is widely deployed.
>
> So we must either let it go (solution #1), or come up with some
> API-lev
(cc-ing Elijah Newren for the points about merging)
Hi again,
To avoid the other thread shadowing more important things:
Michael Muré wrote:
> Someone suggested in the Hacker News thread [0] to post it here as well.
Thanks to Ævar for that.
[...]
> git-bug use as identifier the hash
Here was my reasoning for the naming choice:
- I need something meaningful
- I need something that encompass the idea and features of a bug
tracker because the narrower ideas and actions will be in sub commands
- other projects already used other words, in particular "issue"
- it kind
is to have a workflow similar as what git does, to be
versatile and leave to the users the choice of the topology they want
to use. Obviously, it will be most of the time a single remote where
they collaborate.
As a bug tracker is a different workflow than regular code, there will
be some tooling
(cc-ing Scott)
Hi Junio,
Junio C Hamano wrote:
> Michael Muré writes:
>> I released today git-bug, a distributed bug tracker that embeds in
>> git. It use git's internal storage to store bugs information in a way
>> that can be merged without conflict. You can push
, we're pretty close to having a
rebase-without-touching-index-or-worktree that we can make accessible
to other scripts like git-bug. However, we have to have a pretty good
answer about what to do when we hit conflicts.
[1]
https://public-inbox.org/git/nycvar.qro.7.76.6.180616000...@tvgsbejvaqbjf.bet/
[+cc Stefan Monnier]
Jonathan Nieder writes:
> (cc-ing Scott)
[...]
> I believe you're thinking of TicGit[1].
>
> Some other related work is listed at [2]. Most of these projects have
> gone quiet:
>
> - ditz[3]
> - git-issues[4]
> - cil[5]
> - Bugs Everywhere[6]
> - milli by Steve Kemp, whic
(+ git-dit authors)
Kyle Meyer wrote:
> Jonathan Nieder writes:
>> I believe you're thinking of TicGit[1].
>>
>> Some other related work is listed at [2]. Most of these projects have
>> gone quiet:
>>
>> - ditz[3]
>> - git-issues[4]
>> - cil[5]
>> - Bugs Everywhere[6]
>> - milli by Steve Kemp, w
mlessly integrating 3rd party tools.
>
> I think we're talking past each other. I haven't proposed any blanket
> policy. I'm saying that "git bug" is a bad name for this tool:
>
> - it's hard to find with search engines
> - it conflicts with s
Compared to die(), using BUG() triggers abort(). That may
give us an actual coredump, which should make it easier to
get a stack trace. And since the programming error for these
assertions is not in the functions themselves but in their
callers, such a stack trace is needed to actually find the
. Specifically, when
copying a directory across sibling directories (see test case),
the new logic would accidentally send that object as an extra.
However, I found a bug in the existing logic. The included test
demonstrates this during the final 'git index-pack' call. It
fails with the mes
Hi,
I believe `remote set-url --add --push` has a bug. Performed tests
with v1.8.0.1 and v1.8.1 (Mac OS X).
Quoting the relevant part of the documentation:
> set-url
> Changes URL remote points to. Sets first URL remote points to matching
> regex (first URL if no is given
Hello,
Originally, when I first had Git Bash everything was working
perfectly. Randomly one day, my bash commands were not working. I
uninstalled Git Bash an reinstalled it. I have been trying for 3 weeks
to get it to work again. I am working on Windows 10. I have tried
editing the PATH variables
i committed my changes, then ran
git reset --soft HEAD^
at this point everything is fine
then i switched branches, and all of my changes vaporized into thin
air. uhhh, is this supposed to happen?
anyway, thank god intellij saves my work for me as i go, so i didn't
have to re-write all my code.
my
OVERVIEW
"git rm" will remove more files than specified. This is either a bug or
undocumented behavior (not in the man pages).
SETUP
1. In a git repository, create an empty directory OR a chain of empty
directories
$ mkdir -p path/to/some/
2. Create a file in the deepest directo
Hi Git team,
Thank you all for create a great tool.
Last week, I updated the last version of git (2.12.0 x64-Windows) and
all Unicode characters are display un-correctly. You can see:
http://imgur.com/a/eriKQ
--
Dzung Dang Minh - Software Engineer
Email: dungd...@gmail.com
Phone: (+84) 94.505.10
Hi guys,
I've been using git subtrees extensively to include third party tools
in my projects. Today I stumbled across a bug with git-subtree when I
was trying to update the jacoco (https://github.com/jacoco/jacoco.git)
subtree in one of my projects.
The problem stems from adding a project
On Wed, Aug 30, 2017 at 11:25:00PM +0200, Aleksandar Pavic wrote:
> I have a file
>
> app/Controller/CustomerCardVerificationController.php
>
> And when I take a look at changes log, I get this (no matter which tool I
> use):
>
> 2017-07-31 19:41 dule o membership renew payment ema
The following answer that I got back in 2015 from Jeff King might be
relevant to your problem:
https://marc.info/?l=git&m=144178948506788&w=2
Regards,
Dov
On Thu, Aug 31, 2017 at 9:36 AM, Kevin Daudt wrote:
> On Wed, Aug 30, 2017 at 11:25:00PM +0200, Aleksandar Pavic wrote:
>> I have a file
>>
Hm, thanks, but the link was not helpful, there are no merge commits to
master branch.
Those changes should have not been undone, that's how we caught it,
because 1 line peace of code introduced new feature (+-10% tolerance on
credit card verification amount).
So most likeley they were undo
On 08/31/2017 08:36 AM, Kevin Daudt wrote:
> On Wed, Aug 30, 2017 at 11:25:00PM +0200, Aleksandar Pavic wrote:
>> I have a file
>>
>> app/Controller/CustomerCardVerificationController.php
>>
>> And when I take a look at changes log, I get this (no matter which tool I
>> use):
>>
>> 2017-07-31 19:
On Wed, Aug 30, 2017 at 11:25:00PM +0200, Aleksandar Pavic wrote:
> I have a file
>
> app/Controller/CustomerCardVerificationController.php
>
> And when I take a look at changes log, I get this (no matter which tool I
> use):
>
> 2017-07-31 19:41 dule o membership renew payment em
Hi Ilija,
On 30 January 2018 at 10:21, Ilija Pecelj wrote:
> Though it might not be considered a bug 'per se' it is definitely wired.
> Namely, when you type 'yes' word and hit enter in git bash for widnows, the
> process enters infinite loop and just prints 'y&
On Tuesday 30 January 2018 05:32 AM, Andrew Ardill wrote:
> Hi Ilija,
>
> On 30 January 2018 at 10:21, Ilija Pecelj wrote:
>> Though it might not be considered a bug 'per se' it is definitely wired.
>> Namely, when you type 'yes' word and hit enter in gi
> I think I have identified an obscure bug. I have a reproducible test case.
> I am trying to come up with enough of a test case that can be used for
> finding and fixing the issue.
BTW, I have tested this on 1.7.6.6 and 2.5.0. Same results on either version.
--
To unsubscribe from
My apologies if this has already been reported, but I ran into an
interesting bug with worktrees. In particular, I have an alias 'st'
that maps to 'status -sb'. When running this under a subdirectory of
a worktree created with 'git worktree add', it fails comp
If you have a folder named ~/.gitconfig instead of a file with that
name, when you try to run some global config editing command it will
fail with a wrong error message:
"fatal: Out of memory? mmap failed: No such device"
You can reproduce it:
$rm ~/.gitconfig
$mkdir ~/.gitconfig
$ls -l
any commits in the new
repo
I would like to fix the trival bug myself can some one point me in the
right direction to fix it
--
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
Am 07.06.2016 um 21:20 schrieb Eric Frederich:
> Hello,
>
> I couldn’t find any documentation on submitting patches for gitk.
> I saw in Documentation/SubmittingPatches that gitk is maintained in
> its own repo.
> I can’t clone repo’s unless they’re http while on my corporate proxy.
> I’m hoping s
Am 08.06.2016 um 11:40 schrieb stefan.na...@atlas-elektronik.com:
> Am 07.06.2016 um 21:20 schrieb Eric Frederich:
>> Hello,
>>
>> I couldn’t find any documentation on submitting patches for gitk.
>> I saw in Documentation/SubmittingPatches that gitk is maintained in
>> its own repo.
>> I can’t clo
Thanks for confirming. I do a similar workaround too.
The issue is when new Git users don't even have a ~/.config/git/gitk to modify.
They first have to run it natively where lime exists, then they can
edit it and use it over VNC.
I cannot find any instructions for submitting patches to the gitk
+cc: Paul Mackerras
Am 08.06.2016 um 14:31 schrieb Eric Frederich:
> Thanks for confirming. I do a similar workaround too.
> The issue is when new Git users don't even have a ~/.config/git/gitk to
> modify.
> They first have to run it natively where lime exists, then they can
> edit it and use i
On Wed, Jun 8, 2016 at 8:31 AM, Eric Frederich wrote:
> Thanks for confirming. I do a similar workaround too.
> The issue is when new Git users don't even have a ~/.config/git/gitk to
> modify.
> They first have to run it natively where lime exists, then they can
> edit it and use it over VNC.
>
On Sat, Apr 2, 2016 at 8:25 PM, Benjamin Sandeen
wrote:
> Today, I managed to create a duplicate branch in a git repository. While
> this may not be a bug per se, I do think that it is confusing and some way
> of preventing such issues in the future may be helpful.
This can be confusi
Hi,
On Sat, Apr 2, 2016 at 5:25 PM, Benjamin Sandeen
wrote:
> Today, I managed to create a duplicate branch in a git repository. While
> this may not be a bug per se, I do think that it is confusing and some way
> of preventing such issues in the future may be helpful.
>
> I f
I’m encounter a problem due to my own stupidity…
#1 I pushed a project named Android to my repository.
#2 I `mv Android android`, cause I think it’s no good to use the uppercase as
my project name.
#3 I pushed it to my repository again…
I found that there `Adnroid` and `android` exist in my repo
Both windows and linux support links but both git and the git bash
seem to have a problem with them.
In my source, (originally on Linux) I have a link in my source
directory to a config file which I normally import into python. This
allows me to have something.py pointing to config.txt . config.
Please mention the version no of git you are using and your system.
I am answering according to git 2.8.1 Lubuntu 15.04
On Fri, May 13, 2016 at 10:34 AM, 李本超 wrote:
> Hi all,
>
> Yestoday when I worked using Git, I found a bug. It's about
> rebase. Or I don't know
1 - 100 of 2243 matches
Mail list logo
