Zeger-Jan van de Weg (1):
Git config allows value setting from stdin
Documentation/git-config.txt | 5 -
builtin/config.c | 23 +--
t/t1300-config.sh| 11 +++
3 files changed, 36 insertions(+), 3 deletions(-)
--
2.23.0
, the value cannot
be passed and is read through stdin.
Signed-off-by: Zeger-Jan van de Weg
---
Documentation/git-config.txt | 5 -
builtin/config.c | 23 +--
t/t1300-config.sh| 11 +++
3 files changed, 36 insertions(+), 3 deletions(-)
diff
s/git rev-parse --git-path hooks/post-commit"
as part of the process works fine but it seems a bit inefficient.
Sincerely
Jan
DIR in git-commit.strace
- execve(".git/hooks/post-commit", [... "GIT_DIR=.git" ...
$ cat ~/.gitconfig
[core]
hooksPath = /home/atom/dev/git-hooks
git version 2.21.0
Sincerely
Jan
a.sh
Description: application/shellscript
he gui and then close the gui
for the script to finish.
Script output:
command-line: access("/home/atom/dev/git-hooks/post-commit", X_OK)
gui: access(".git/hooks/post-commit", X_OK)
$ cat ~/.gitconfig
[core]
hooksPath = /home/atom/dev/git-hooks
git version 2.21.0
Sincerely
Jan
a.sh
Description: application/shellscript
ile24
4. Unstage line2 from commit (see the attached screenshot)
5. >>> "Unstaged Changes" windowpane resets <<<
Sincerely
Jan
On Sun, 31 Mar 2019 at 21:15, Bert Wesarg wrote:
>
> Hi Jan,
>
> On Sun, Mar 31, 2019 at 8:45 PM Jan Ziak <0xe2.0x9a.0...@gmail.com> wrote:
> >
> > Hello
> >
> > After performing "Unstage Line From Commit" action, the "Unstaged
> &g
Hello
git gui is missing a search functionality in the "Portions staged for
commit" windowpane.
Ctrl+F key combination currently has the same effect as the PageDown key.
git version 2.21.0
Sincerely
Jan
Hello
After performing "Unstage Line From Commit" action, the "Unstaged
Changes" windowpane is reset. The reset does not happen with "Unstage
Hunk From Commit" action.
git version 2.21.0
Sincerely
Jan
shadow,Natural shadow
Photo Retouching Service
Photo Retouching, Glamour Retouching.
Our Service is 24-48 hours but we can deliver the images sooner in case of
emergency.
We can give you editing test on your photos.
We do unlimited revisions until you are satisfied with the work.
Thanks,
Jan Williams
ta connected with a fact that test restarts daemon few times. I can barely
wrap my head around it but I guess it's somewhat around "shell still tries to
read fifo while attempt to create new one is made".
Regards
Jan
content might possibly land in the file after zeroing.
The reason I'm asking is because /bin/sh in my distribution (mksh) actually
manifests the issue -- test fails because at the time of grep output was not
processed yet (fixed by sleep 1 before grep). Also there is an issue with output
of previous test landing in daemon.log despite ">daemon.log".
Regards
Jan
ot;: "abcd1234", "summary": "Implement loop",
"characters": ")" },
{ "commit": "d1234abc", "summary": "Add missing
semicolon", "characters": ";" },
{ "commit": "abcd1234", "summary": "Implement loop",
"characters": " }" }
]
What would be the most direct way to achieve such a character-based
blame/annotate? Should I write some sort of Git extension, or hack
into Git's source code?
E.g. I looked for an option in `git-blame` or `git-annotate` to change
the "next line boundary" from "carret return" (line-based blame) to
"any whitespace" (word-based blame) or "character-by-character"
(character-based blame), but I didn't find it. Could this be
implemented in `blame.c`? If so, which methods would need tweaking?
Many thanks!
Jan
Hello there,
I would like to ask how can I uninstall Git?
Kind regards
Jan
"b" to "x"
git rebase -i HEAD^1 -p
git log -1
# here, you can see the bad merge commit message
Regards
Jan
I have been trying to reach you contact
me--(jonathansymonds...@hotmail.com) for more details
On Tue, 2017-10-03 at 05:10 -0400, Jeff King wrote:
> I dunno. Maybe I am wrong, because certainly I never set it. We've
> had
> two reports on the list since v2.14.2. The motivation for the first
> was
> "I have no idea why I set that, and I'll switch to auto". This is the
> second.
>
I also cam
> On 20. Aug 2017, at 12:27 , Andreas Heiduk wrote:
>
> Am 19.08.2017 um 14:45 schrieb Jan Teske:
>> Is there any way to fix such branches from subfolders in a way that they
>> integrate correctly with the converted git repository, without losing any
>> (or at least
Hello,
I’m trying to do a one-time conversion of a large SVN repository to git using
git-svn. Unfortunately, this SVN repo contains a substantial amount of
non-standard branches created from a subfolder of trunk/. Users that only need
to work on part of the code inside the repo usually create s
`git init .` inside the extracted tarball, or maybe
`git clone `?
Many thanks,
Jan Keromnes
On Wed, Jul 19, 2017 at 12:16 PM, Jan Keromnes wrote:
> Hello,
>
> I'm trying to build a profile-optimized Git. I used to do this with
> the following commands:
>
> mkdir /tmp/git
&
at a similar problem
was already fixed for `make profile`:
http://git.661346.n2.nabble.com/make-profile-issue-on-Git-2-1-0-td7616964.html
Is it possible that the above commit fixed `make profile`, but not
`make profile-fast`?
Or, is there a good way for me to work around this issue?
Many thanks,
Jan Keromnes
; private ones (e.g., refs/mirror/* in addition to your branches in
> refs/heads/*). The obvious downside is that anybody cloning your
> downstream mirror doesn't pick up refs/mirror unless they configure
> that refspec explicitly.
This sounds very useful. How would one go about setting up this
configuration?
--
Kind regards,
Jan Danielsson
tream:
cd $DSTDIR
git remote update --prune
git push
This seems to accomplish everything I want except that the the "git
push" deletes any branches I have created on my self-hosted repository.
Am I doing it completely wrong? If not, how do I make my branches
survive the push?
--
Kind regards,
Jan Danielsson
able sending a whole patch
set in 2 rounds manually. But I didn't find any way how to do it right.
Regards
Jan
> >
> > I wonder if something like this would Just Work for this case without
> > any configuration or command-line options, with the added benefit of
&g
; @@ -358,6 +366,8 @@ $rc = GetOptions(
> "force" => \$force,
> "xmailer!" => \$use_xmailer,
> "no-xmailer" => sub {$use_xmailer = 0},
> + "batch-size=i" => \$batch_s
Hello, thank you for posting this improvement. I've been missing such feature
in git. I hope to test it soon.
Jan Viktorin
RehiveTech
Sent from a mobile device
Původní zpráva
Od: xiaoqiang zhao
Odesláno: pondělí, 1. května 2017 15:00
Komu: git@vger.kernel.org
Kopie: gits...@pobox.com;
On 22.03.2017 13:08, Junio C Hamano wrote:
> Please respond to the list, saying it is OK to add your "sign-off"
> (see Documentation/SubmittingPatches) to these patches.
Please feel free to do so and thanks for handling the issue.
Regards
Jan
It appears more tests are affected:
$ grep -r '^[[:space:]]*EOF &&' .
./t7406-submodule-update.sh:EOF &&
./t7030-verify-tag.sh: EOF &&
./t7030-verify-tag.sh: EOF &&
./t7004-tag.sh: EOF &&
./t7004-tag.sh: EOF &&
attaching patch for t7406 and t7030 which both fail even after fix is
applied
accordingly
Note that I'm not subscribed to mailing list so in case of any questions
please mail me directly.
Regards
Jan
diff -urN git-2.11.1.orig/t/t5615-alternate-env.sh
git-2.11.1/t/t5615-alternate-env.sh
--- git-2.11.1.orig/t/t5615-alternate-env.sh2017-02-03 02:24:45.115143042
Current version: 2.10.2
Example workflow:
* I would do a global substitution across a source tree, e.g. `perl -i
-pe 's{OLD_FOO\(x\)}{NEW_BAR(x, 0)}' *.c`
* Using `git add -p`, I would verify each of the substitutions that they
make sense in their respective locations, and, based on that,
More
details below, and I can provide further debug information if you
don't already know the problem.
Thanks,
Jan
[0] "`make profile-install` fails in 2.9.3" -
https://marc.info/?l=git&m=147274608823171&w=2
[1] "Fwd: Git 2.8.1 fails test 32 of t7300-clean.sh, breaks prof
roblem.
Thanks,
Jan Keromnes
---
Steps to reproduce:
curl https://www.kernel.org/pub/software/scm/git/git-2.9.3.tar.xz | tar xJ \
&& cd git-2.9.3 \
&& make prefix=/usr profile-install install-man -j18
Expected result:
- runs all tests to get a profil
o the list.
Thanks
Jan
The pre-receive hook from my quick testing => press Ctrl-C on the client
when it is busy processing the 'sleep 5'
In my testing I was committing/pushing 32MB+ binary files that take some
time to process.
#!/bin/bash
trap 'echo TRAP >> /tmp/gittest/
rom the line "Removing possible_sub1/", it looks like Git
2.8.2 removes a possible submodule while executing `git clean -f -d`,
whereas the test expects it not to.
Is it possible to make Git's output even more verbose, so that it
tells why it decides to remove "possible_sub1&q
On Sat, Apr 30, 2016 at 3:19 AM, David Aguilar wrote:
> On Wed, Apr 27, 2016 at 11:12:25AM +0200, Jan Smets wrote:
>> Hi
>>
>> Please consider following example
>>
>> #!/bin/bash
>> rm -rf /tmp/gittest
>> mkdir /tmp/gittest
>> cd /tmp/gittest
chmod 0 possible_sub1/.git &&
# >to_clean/should_clean.this &&
# git clean -f -d &&
# test_path_is_file possible_sub1/.git &&
# test_path_is_file possible_sub1/hello.world &&
# test_pa
executing git difftool with the -d option :
/usr/lib/git-core/git-difftool line 260: File exists
A possible solution is to build an unique list in @working_tree
The purpose is to edit/resolve the conflict in the difftool.
Thanks!
--
Smets Jan
j...@smets.cx
--
To unsubscribe from this list: send
> One thing I wondered about is whether this should be enabled by
> default or not. Long-time users of git-p4 might be a bit surprised to
> find their git commits suddenly gaining an extra Job: field.
I thought about that too when but then I realized that there's no
switch for the reverse directio
> By the way, you may or may not have noticed that I've been
> reordering the lines of your message quoted in my responses; around
> here, top-posting is frowned upon.
I haven't noticed. Thanks for pointing out.
As for the submitGit cover letter I wanted to raise at least an issue
(if not create
same as for one of the commits.
Maybe submitGit tried to be smart there? Or maybe it just really
doesn't support it (yet?).
On Tue, Apr 19, 2016 at 11:09 PM, Junio C Hamano wrote:
> Jan Durovec writes:
>
>> On Tue, Apr 19, 2016 at 8:50 PM, Jan Durovec wrote:
>>>> Any
Huh... seems that it works :)
v3 sent in 2 parts
On Tue, Apr 19, 2016 at 8:50 PM, Jan Durovec wrote:
>> Any submitGit users? I think it lets you throw multiple-patch
>> series just fine. In this case, you'd prepare a two patch series on
>> a branch, 1/2 being the cle
commit messages on git side).
The jobs are added to the message in the same format as is expected when
migrating in the reverse direction.
Signed-off-by: Jan Durovec
---
git-p4.py | 12 ++
t/lib-git-p4.sh| 9 +
t/t9829-git-p4-jobs.sh | 99
Preliminary clean-up of testing libraries for git-p4.
* spaces added to both sides of () in function definitions in lib-git-p4
* tab indentation added to git-p4 tests when <<- redirection is used
Signed-off-by: Jan Durovec
---
t/lib-git-p4.sh | 24 +++
t
> Any submitGit users? I think it lets you throw multiple-patch
> series just fine. In this case, you'd prepare a two patch series on
> a branch, 1/2 being the clean-up and 2/2 being the new feature, and
> if you give that branch to submitGit as a whole it should do the
> right thing, I'd imagine
owing patch I'll
* add spaces before () for functions in t/lib-git-p4.sh
* remove name local variable in p4_add_job/user in t/lib-git-p4.sh
* fix t/t98* leading tabs where <<- is used
On Tue, Apr 19, 2016 at 7:47 PM, Junio C Hamano wrote:
> Jan Durovec writes:
>
>> given t
(see t/t9826...)
...is there anything left to fix in this patch or is it good as is?
I.e. would you prefer me to change the code mentioned above at the cost
of code style consistency?
Is there something else that I have missed in my enumeration?
Regards,
Jan
On Tue, Apr 19, 2016 at 6:45 PM, Junio
commit messages on git side).
The jobs are added to the message in the same format as is expected when
migrating in the reverse direction.
Signed-off-by: Jan Durovec
---
git-p4.py | 12 ++
t/lib-git-p4.sh| 10 +
t/t9829-git-p4-jobs.sh | 99
e advise how to mark it as executable? Does it need to be
added to some configuration file? Or am I interpreting the error
message incorrectly?
Regards,
Jan
On Sat, Apr 16, 2016 at 12:10 AM, Luke Diamand wrote:
> On 15 April 2016 at 21:27, Junio C Hamano wrote:
>> Jan Durovec writes
---
git-p4.py | 12
1 file changed, 12 insertions(+)
diff --git a/git-p4.py b/git-p4.py
index 527d44b..a81795f 100755
--- a/git-p4.py
+++ b/git-p4.py
@@ -2320,6 +2320,15 @@ def extractFilesFromCommit(self, commit):
fnum = fnum + 1
return files
+def extract
Hi,
this patch makes it possible to use --show-linear-break in `git log --graph
--oneline --all`.
(Please Cc me on replies, I'm not subscribed to the Git ML.)
Cheers,
Jan
--
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/From 1ac6bb7c31652835d3d046c82e423f0cea6e090
just fine when describing master:
$ git describe master
v4.2-2-g34eb80b
$ git describe master --match=v4.1
v4.1-1046-g34eb80b
However when I merged master into next, it started producing those incorrect
results.
--
- Jan Hudec
--
To unsubscribe from this list: send the line &q
like
to hear them.
Thank you
- Jan
--
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
27;git gc --prune=now/all' on the bare repository
could end with this message:
$ git gc --prune=all
error: refs/heads/master does not point to a valid object!
fatal: bad object refs/heads/master
error: failed to run repack
$ git log -1
fatal: bad object HEAD
This behaviour has been observed
, it works as a whitelist
of allowed mechanisms for authentication selected from the ones
supported by the installed SASL perl library.
Signed-off-by: Jan Viktorin
---
Documentation/git-send-email.txt | 11 +++
git-send-email.perl | 26 +-
2 files
On Sun, 9 Aug 2015 14:13:33 -0400
Eric Sunshine wrote:
> On Wed, Aug 5, 2015 at 3:17 AM, Jan Viktorin
> wrote:
> > Do I understand well that you are complaining about too
> > narrow commmit message?
>
> Yes, I'm a complainer. ;-) It's minor, though, not a big
however, the
errors file is always empty.)
* Is there any other place where the files out, errors are placed?
* I have no idea what the fake.sendmail does (I could see its contents
but still...). Is it suitable for my tests?
* Should I check the behaviour '--smtp-auth overrides
sendemail.s
On Sun, 02 Aug 2015 11:28:49 -0700
Junio C Hamano wrote:
> Jan Viktorin writes:
>
> > Authen::SASL gives:
> >
> > No SASL mechanism found
> > at /usr/share/perl5/vendor_perl/Authen/SASL.pm line 77.
> > at /usr/share/perl5/core_perl/Net/SMTP.pm line 20
I've already mentioned. at least, it filters out the
unwanted characters like '/', '.', etc.
Regards
Jan
On Sun, 2 Aug 2015 05:41:29 -0400
Eric Sunshine wrote:
> On Sat, Aug 1, 2015 at 2:19 PM, Jan Viktorin
> wrote:
> > On Sat, 1 Aug 2015 05:33:28 -0400 Eric Suns
,
it works as a whitelist of allowed mechanisms for
authentication selected from the ones supported by
the installed SASL perl library.
Signed-off-by: Jan Viktorin
---
Changes v1 -> v2:
- check user input by regex
- added documentation
- still missing a test
Documentation/git-send-email.
Hello Brian,
thanks for your note. I think, I will remove the check
of list of mechanisms and put there a regex check.
On Sat, 1 Aug 2015 16:49:59 +
"brian m. carlson" wrote:
> On Sat, Aug 01, 2015 at 01:33:37AM +0200, Jan Viktorin wrote:
> > + # Do not allo
at, 1 Aug 2015 05:33:28 -0400
Eric Sunshine wrote:
> On Fri, Jul 31, 2015 at 7:33 PM, Jan Viktorin
> wrote:
> > When sending an e-mail, the client and server must
> > agree on an authentication mechanism. Some servers
> > (due to misconfiguration or a bug) denies vali
defined, it works as a whitelist
of allowed mechanisms for authentication. There
are four mechanisms supported: PLAIN, LOGIN,
CRAM-MD5, DIGEST-MD5. However, their availability
depends on the installed SASL library.
Signed-off-by: Jan Viktorin
---
git-send-email.perl | 31
finitely files changed in too! (and show up in latest.zip.files)
Is there a limit of files git archive can process?
lg
Jan Vales
--
I only read plaintext emails.
Someone @ irc://irc.fsinf.at:6667/tuwien
webIRC: https://frost.fsinf.at/iris/
signature.asc
Description: OpenPGP digital signature
On 17.06.2015 18:42, Junio C Hamano wrote:
Jan-Philip Gehrcke writes:
I was surprised to see that the output of
git log --encoding=utf-8 "--format=format:%b"
can contain byte sequences that are invalid in UTF-8. Note: I am using
git 2.1.4 and the %b format specifier repr
On 15.06.2015 18:21, Torsten Bögershausen wrote:
On 2015-06-15 10.50, Jan-Philip Gehrcke wrote:
Let me describe what I think it currently does:
The program attempts to re-code a log message, so it follows the chain
raw input -> unicode -> raw output
Not sure what "raw i
larify what actually happens behind the scenes. What do you think?
Cheers,
Jan-Philip Gehrcke
--
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
agine people
really *want* to see all the tags). So printing all such tags would let
them select the desired tag with grep or some more elaborate scripting...
Just a thought.
Honza
--
Jan Kara
SUSE Labs, CR
--
To unsubscribe from this
On Thu, 20 Feb 2014 12:06:17, Michael Haggerty wrote:
>On 02/19/2014 11:58 PM, Jan Engelhardt wrote:
>>
>> Looking at it from one more angle, `git fetch r --tags` and
>> `git push r --tags` is now no longer symmetric :(
>
>I'm glad you brought this up, bec
On Thursday 2014-02-20 00:40, Junio C Hamano wrote:
>On Wed, Feb 19, 2014 at 2:58 PM, Jan Engelhardt wrote:
> Looking at it from one more angle, `git fetch r --tags` and
>`git push r --tags` is now no longer symmetric :(
>
>
>I would have loved to hear such comments _duri
On Wednesday 2014-02-19 21:01, Junio C Hamano wrote:
>Jan Engelhardt writes:
>> The release notes for 1.9.0 read:
>>
>>> * The "--tags" option to "git fetch" no longer tells the command to
>>> fetch _only_ the tags. It instead fetches tag
release notes should also say -- like it was done
extensively for git add -- how to get back the old
behavior (perhaps through now-different commands).
thanks,
Jan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More ma
On Thursday 2013-05-23 20:16, Bernhard R. Link wrote:
>>
>> Not sure if German users would know what "hunk" means, in case we
>> leave it untranslated. And I'm not sure if I would understand "Kontext".
>> I tend to leave it untranslated.
>
>Anyone found a German translation of the Patch manpage? T
On Wednesday 2013-05-22 17:52, Holger Hellmuth (IKS) wrote:
>>
>> Not sure if German users would know what "hunk" means, in case we
>> leave it untranslated. And I'm not sure if I would understand "Kontext".
>> I tend to leave it untranslated.
>
> I don't think "Bereich" is a bad choice. As "hunk"
On Wednesday 2013-05-15 17:31, Holger Hellmuth (IKS) wrote:
>>>
>>> I actually had the '-' in there too until I tried to look up "Zip-Datei"
>>> in the Duden. While I don't get the leading '.' (I cannot remember having
>>> seen that anywhere, AFAIK the file extensions are always used without the
>
On Wednesday 2013-05-15 14:27, Jens Lehmann wrote:
>>
>> While it's spoken Packdatei, the way to actually write it is
>> .pack-Datei or ".pack"-Datei.
>
>I actually had the '-' in there too until I tried to look up "Zip-Datei"
>in the Duden. While I don't get the leading '.' (I cannot remember hav
On Wednesday 2013-05-15 13:26, Jens Lehmann wrote:
>
>Hmm, I rather tend towards using "Repository" instead of "Archiv" too, as
>"Archiv" can mean anything from a tar-file to a git repository
It's exactly the reasoning I made in my git-glossary.txt sample
(of which the reasoning apparently has no
On Monday 2013-05-13 20:57, Ralph Haußmann wrote:
>
>There is a glossary for the pro-git book (see [2]) but it is not up-to-date
>and it is also mixed. Therefor I would like to avoid using this glossary.
>I like the idea of a shared wiki (git de.po and pro-git).
>I suggest a single page as over
On Monday 2013-05-13 14:54, Thomas Rast wrote:
>As I am sure you are all aware, there are two main religions as to how
>one can translate technical material into German: leave the technical
>terms mostly in English, or translate them to an appropriate
>corresponding word. I'll denote them G+E and
Am Dienstag, den 23.04.2013, 22:50 +0200 schrieb Johan Herland:
> On Tue, Apr 23, 2013 at 4:59 PM, Junio C Hamano wrote:
> > Jan Weitzel writes:
> >
> >> Hello,
> >> I have the following problem: I have 2 bare git repositories one has
> >> several br
Am Dienstag, den 23.04.2013, 13:25 +0200 schrieb Johan Herland:
> On Tue, Apr 23, 2013 at 12:53 PM, Jan Weitzel wrote:
> > Hello,
> > I have the following problem: I have 2 bare git repositories one has
> > several branches and tags.
> > If I try this in the second r
is to fetch only specific branches and the related tags.
Jan
--
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
Duy Nguyen wrote:
> On Sat, Mar 30, 2013 at 8:45 PM, Jan Larres wrote:
>> I would expect the last command to also report 'set'. I've also tried
>> other patterns like 'foo/' and 'foo*', but it didn't make any
>> difference.
>
>
pose archiving tool/helper for the
repository rather than just something for the special cases of tars and
zips. But I guess that's somewhat subjective.
Cheers,
Jan
--
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
'unspecified'. More precisely:
$ git init test
Initialized empty Git repository in /home/jan/test/.git/
$ cd test
$ mkdir foo
$ touch foo/bar
$ echo "foo export-ignore" > .gitattributes
$ git check-attr export-ignore foo
foo: export-ignore: set
$ git check-attr export-ignore foo/bar
copy)
Is there some way how to do it without swithing to each branch and update
them manually?
Thanks,
Jan
--
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
added to 1.5.x in this merge has a '*' suffix
for 1.5.x\www.
This '*' is the marker for a non-inheritable mergeinfo range.
The '*' means that only the path on which the mergeinfo is explicitly set has
had this range merged into it.
Signed-off-by: Jan Pesta
---
per
he path on which the mergeinfo is explicitly set
has had this range merged into it.
Signed-off-by: Jan Pesta
---
perl/Git/SVN.pm | 5 +
1 file changed, 5 insertions(+)
diff --git a/perl/Git/SVN.pm b/perl/Git/SVN.pm
index 0ebc68a..74d49bb 100644
--- a/perl/Git/SVN.pm
+++ b/perl/Git/SVN
Hi Junio,
You have right. But I think if there is a "*" sign, it should be skiped,
instead of failing on comparing string with a number.
I will prepare another patch.
Regards,
Jan
Kind regards / S pozdravem
Jan Pešta
SW Engineer Sr.
CertiCon a.s., www.certicon.cz
Vaclavska 12
12
e marker for a non-inheritable mergeinfo range.
The '*' means that only the path on which the mergeinfo is explicitly set
has had this range merged into it.
Signed-off-by: Jan Pesta
---
perl/Git/SVN.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/perl/Git/SVN.pm b/perl/Git/SVN.pm
inde
Hi again,
Finally I created patch according to document.
Please have a look on referenced site for more details.
Currently I have a problems in our project, where SVN is main repository and
merge-info contains "*" which causes troubles in SVN.pm.
Regards,
Jan
Kind regards / S pozdr
Sorry,
My fault :)
Here is a patch atached.
Jan
Kind regards / S pozdravem
Jan Pešta
SW Engineer Sr.
CertiCon a.s., www.certicon.cz
Vaclavska 12
12000 Prague 2
Czech Republic
Office Prague: +420 224 904 406
Mobile: +420 604 794 306
E-mail: jan.pe...@certicon.cz
-Original Message
Hi,
I found a problem when using GIT-SVN.
In inproperly merges in SVN causes that the ranges contains additional
character "*".
Attached patch fix this issue, I have it already tested for several months.
Regards,
Jan
Kind regards / S pozdravem
Jan Pešta
SW Engineer Sr.
Ce
grate it upstream?
Regards
Jan Rüegg
--
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 Tuesday 2012-10-02 10:26, Johannes Sixt wrote:
>
>Note that git commit -m A --allow-empty *DID* create a commit. Only, that
>it received the same name (SHA1) as the commit you created before it
>because it had the exact same contents (files, parents, author, committer,
>and timestamps). Obvious
On Wednesday 2012-10-03 21:03, Junio C Hamano wrote:
>
>I said that "git reset --keep" started out as an ugly workaround for
>the lack of "git checkout -B $current_branch". Now we have it, so
>we can afford to make "reset --keep" less prominently advertised in
>our tool set. As I already said ba
e very first
version (3714e7c8)?! (And it wasn't present in the version on the mailing
list: http://article.gmane.org/gmane.comp.version-control.git/35221)
Regards
Jan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kern
plementation in master:
#define isprint(x) ((x) >= 0x20 && (x) <= 0x7e)
To summarize my opinion:
I no longer see a reason to correct isspace() (unless somebody with an actual
use case complains), and a more POSIXly isprint() is already in master.
=> Nothing to do. :)
Regards
Jan
--
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
Thái Ngọc Duy
> ---
> I wrote a small C program to compare the result of all is* functions
> that Git replaces against the libc version. These are the only ones that
> differ. Which matches what Jan Schönherr commented.
>
> ctype.c | 6 +++---
> git-compat
From: Jan H. Schönherr
git-format-patch does currently not parse user supplied extra header
values (e. g., --cc, --add-header) and just replays them. That forces
users to add them RFC 2822/2047 conform in encoded form, e. g.
--cc '=?UTF-8?q?Jan=20H=2E=20Sch=C3=B6nherr?= <...>
From: Jan H. Schönherr
According to RFC 2047 and RFC 822, rfc2047 encoded words and and rfc822
quoted strings do not mix. Since add_rfc2047() no longer leaves RFC 822
specials behind, the quoting is also no longer necessary to create a
standard-conform mail.
Remove the quoting, when RFC 2047
1 - 100 of 147 matches
Mail list logo
