<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/git-cvsimport.perl, branch v2.26.0-rc2</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v2.26.0-rc2</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v2.26.0-rc2'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2019-11-10T07:00:54Z</updated>
<entry>
<title>Fix spelling errors in messages shown to users</title>
<updated>2019-11-10T07:00:54Z</updated>
<author>
<name>Elijah Newren</name>
<email>newren@gmail.com</email>
</author>
<published>2019-11-05T17:07:26Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=96c0caf5e303c189cc528fe67703828e1ffacfb2'/>
<id>urn:sha1:96c0caf5e303c189cc528fe67703828e1ffacfb2</id>
<content type='text'>
Reported-by: Jens Schleusener &lt;Jens.Schleusener@fossies.org&gt;
Signed-off-by: Elijah Newren &lt;newren@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>perl: call timegm and timelocal with 4-digit year</title>
<updated>2018-02-23T22:47:06Z</updated>
<author>
<name>Bernhard M. Wiedemann</name>
<email>bwiedemann@suse.de</email>
</author>
<published>2018-02-23T17:20:45Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=a40e06ee336d608cfe0928d91d2b44112d8fd1e2'/>
<id>urn:sha1:a40e06ee336d608cfe0928d91d2b44112d8fd1e2</id>
<content type='text'>
Amazingly, timegm(gmtime(0)) is only 0 before 2020 because perl's
timegm deviates from GNU timegm(3) in how it handles years.

man Time::Local says

 Whenever possible, use an absolute four digit year instead.

with a detailed explanation about ambiguity of 2-digit years above that.

Even though this ambiguity is error-prone with &gt;50% of users getting it
wrong, it has been like this for 20+ years, so we just use 4-digit years
everywhere to be on the safe side.

We add some extra logic to cvsimport because it allows 2-digit year
input and interpreting an 18 as 1918 can be avoided easily and safely.

Signed-off-by: Bernhard M. Wiedemann &lt;bwiedemann@suse.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>cvsimport: apply shell-quoting regex globally</title>
<updated>2017-12-08T17:02:54Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2017-12-08T09:58:19Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=8c87bdfb2137c9e9e945df13e2f2e1eb995ddf83'/>
<id>urn:sha1:8c87bdfb2137c9e9e945df13e2f2e1eb995ddf83</id>
<content type='text'>
Commit 5b4efea666 (cvsimport: shell-quote variable used in
backticks, 2017-09-11) tried to shell-quote a variable, but
forgot to use the "/g" modifier to apply the quoting to the
whole variable. This means we'd miss any embedded
single-quotes after the first one.

Reported-by: &lt;littlelailo@yahoo.com&gt;
Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>cvsimport: shell-quote variable used in backticks</title>
<updated>2017-09-12T02:10:22Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2017-09-11T14:24:26Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=5b4efea666951efe0770f8d5a301f8917015315f'/>
<id>urn:sha1:5b4efea666951efe0770f8d5a301f8917015315f</id>
<content type='text'>
We run `git rev-parse` though the shell, and quote its
argument only with single-quotes. This prevents most
metacharacters from being a problem, but misses the obvious
case when $name itself has single-quotes in it. We can fix
this by applying the usual shell-quoting formula.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'cn/cvsimport-perl-update'</title>
<updated>2015-06-25T18:08:08Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-06-25T18:08:08Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=c82b6d3f4ba871ef65e25f9c336eb7c46f92e367'/>
<id>urn:sha1:c82b6d3f4ba871ef65e25f9c336eb7c46f92e367</id>
<content type='text'>
* cn/cvsimport-perl-update:
  cvsimport: silence regex warning appearing in Perl 5.22.
</content>
</entry>
<entry>
<title>cvsimport: silence regex warning appearing in Perl 5.22.</title>
<updated>2015-06-25T00:14:27Z</updated>
<author>
<name>Christian Neukirchen</name>
<email>chneukirchen@gmail.com</email>
</author>
<published>2015-06-24T14:04:20Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=16272c7db4cf647d86de89ee46b248013109529d'/>
<id>urn:sha1:16272c7db4cf647d86de89ee46b248013109529d</id>
<content type='text'>
Since Perl 5.22, "A literal '{' should now be escaped in a pattern".
Silence the recently added warning by using \{ instead.

Signed-off-by: Christian Neukirchen &lt;chneukirchen@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>merge: deprecate 'git merge &lt;message&gt; HEAD &lt;commit&gt;' syntax</title>
<updated>2015-04-29T20:28:10Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-03-26T04:58:45Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=d45366e8aa922037e7e84c3f35924d2b1399a453'/>
<id>urn:sha1:d45366e8aa922037e7e84c3f35924d2b1399a453</id>
<content type='text'>
We had this in "git merge" manual for eternity:

    'git merge' &lt;msg&gt; HEAD &lt;commit&gt;...

    [This] syntax (&lt;msg&gt; `HEAD` &lt;commit&gt;...) is supported for
    historical reasons.  Do not use it from the command line or in
    new scripts.  It is the same as `git merge -m &lt;msg&gt; &lt;commit&gt;...`.

With the update to "git merge" to make it understand what is
recorded in FETCH_HEAD directly, including Octopus merge cases, we
now can rewrite the use of this syntax in "git pull" with a simple
"git merge FETCH_HEAD".

Also there are quite a few fallouts in the test scripts, and it
turns out that "git cvsimport" also uses this old syntax to record
a merge.

Judging from this result, I would not be surprised if dropping the
support of the old syntax broke scripts people have written and been
relying on for the past ten years.  But at least we can start the
deprecation process by throwing a warning message when the syntax is
used.

With luck, we might be able to drop the support in a few years.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-cvsimport: use a lowercase "usage:" string</title>
<updated>2013-02-24T21:31:07Z</updated>
<author>
<name>David Aguilar</name>
<email>davvid@gmail.com</email>
</author>
<published>2013-02-24T00:50:15Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=ce7f3ca89afa7a0fc6f73db44361c8ae2dc31757'/>
<id>urn:sha1:ce7f3ca89afa7a0fc6f73db44361c8ae2dc31757</id>
<content type='text'>
Make the usage string consistent with Git.

Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: David Aguilar &lt;davvid@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>cvsimport: format commit timestamp ourselves without using strftime</title>
<updated>2013-02-09T22:41:49Z</updated>
<author>
<name>Ben Walton</name>
<email>bdwalton@gmail.com</email>
</author>
<published>2013-02-09T21:46:58Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=48c916285753907b71a0ef663576f01ee260095c'/>
<id>urn:sha1:48c916285753907b71a0ef663576f01ee260095c</id>
<content type='text'>
Some implementations of strftime(3) lack support for "%z".  Also
there is no need for %s in git-cvsimport as the supplied time is
already in seconds since the epoch.

For %z, use the function get_tz_offset provided by Git.pm instead.

Signed-off-by: Ben Walton &lt;bdwalton@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>cvsimport: work around perl tzset issue</title>
<updated>2012-11-04T13:02:41Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2012-11-04T12:25:36Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=c2b3af0537e0b2c7624913b0f26191e992beb12c'/>
<id>urn:sha1:c2b3af0537e0b2c7624913b0f26191e992beb12c</id>
<content type='text'>
On many platforms, the first invocation of localtime_r will
check $TZ in the environment, but subsequent invocations
will use a cached value. That means that setting $ENV{TZ} in
the middle of the program may or may not have an effect on
later calls to localtime.  Perl 5.10.0 and later handles
this automatically for us, but we try to remain portable
back to 5.8. Work around it by calling tzset ourselves.
</content>
</entry>
</feed>
