two trivial questions concerning the gitlab repository

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

two trivial questions concerning the gitlab repository

alvinpenner
1. currently, if I compile Inkscape from gitlab, it reports the rev number as follows:
Inkscape 0.92+devel unknown
Are there any plans to include a rev number into this report?

2. currently, if I execute git log, I get the following sequence of commit numbers:
commit 213013a5a08d37bd29da167eece256be75cebe7c
commit 0868ec95edd45394fcf583bf3f1cfa311e8a4c1d
commit f836a482511f299034e84f2e153f31698904f92b
commit 27f13805c97fcb517982009e2bfb3fd9ad6e413f
commit 6e1ecba04f030e650e12edec2ad7a57530c661e4
commit 506e737427861bc1d288c498723d63d56a8075ce
commit 0edfdf950796befdb42ab9b2ef76c76483d9dbb1

where I have edited out the text info. I am not able to detect the chronological sequence of these numbers. I understand that the first 8 digits can be used as a shorthand, but these do not seem to be chronologically ordered either. For purposes of bug tracking it would be very helpful to be able to report a rev number that was chronologically ordered. Are there any plans to do so, or am I missing something really obvious here?

Alvin
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Martin Owens-2
Hi Alvin,

Git doesn't have revision numbers, it just has hashes. In a way this is
good, because you could theoretically prepend commits and the commit
hash would stay the same.

The bad news is that it's not possible to get a solid rev number as
such. You can add up all the revisions so far, but that isn't useful on
the command line.

So we're stuck with non-chronological commit hashes.

Although we can also uses tags, which makes it a bit easier for the
bigger revision markers.

Best Regards, Martin Owens

On Fri, 2017-06-23 at 04:21 -0700, alvinpenner wrote:

> 1. currently, if I compile Inkscape from gitlab, it reports the rev
> number as
> follows:
> Inkscape 0.92+devel unknown
> Are there any plans to include a rev number into this report?
>
> 2. currently, if I execute git log, I get the following sequence of
> commit
> numbers:
> commit 213013a5a08d37bd29da167eece256be75cebe7c
> commit 0868ec95edd45394fcf583bf3f1cfa311e8a4c1d
> commit f836a482511f299034e84f2e153f31698904f92b
> commit 27f13805c97fcb517982009e2bfb3fd9ad6e413f
> commit 6e1ecba04f030e650e12edec2ad7a57530c661e4
> commit 506e737427861bc1d288c498723d63d56a8075ce
> commit 0edfdf950796befdb42ab9b2ef76c76483d9dbb1
>
> where I have edited out the text info. I am not able to detect the
> chronological sequence of these numbers. I understand that the first
> 8
> digits can be used as a shorthand, but these do not seem to be
> chronologically ordered either. For purposes of bug tracking it would
> be
> very helpful to be able to report a rev number that was
> chronologically
> ordered. Are there any plans to do so, or am I missing something
> really
> obvious here?
>
> Alvin
>
>
>
>
> --
> View this message in context: http://inkscape.13.x6.nabble.com/two-tr
> ivial-questions-concerning-the-gitlab-repository-tp4980326.html
> Sent from the Inkscape - Dev mailing list archive at Nabble.com.
>
> -------------------------------------------------------------------
> -----------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Felipe Sanches-2
In reply to this post by alvinpenner
These are the git repo commit hashes. Yes, you are correct that they
do not explicitely convey a cronological ordering. But they
implicitely do so, since they point to specific commits in the git
tree. Since git is distributed, there really no way (as far as I can
tell) of attributing sequential numbers to commits, because there may
be developers creating new commits in their own branches or remote
repos, and there's no central authority emitting such ascending order
numbers.

We could, of course, append a date&time string to the version-id if
the concern is that we'd like to grasp the age of a certain build. If
the concern is bug tracking, then a query to the git tree will show
you precisely where a certain commit is located, based on its hash.

2017-06-23 8:21 GMT-03:00 alvinpenner <[hidden email]>:

> 1. currently, if I compile Inkscape from gitlab, it reports the rev number as
> follows:
> Inkscape 0.92+devel unknown
> Are there any plans to include a rev number into this report?
>
> 2. currently, if I execute git log, I get the following sequence of commit
> numbers:
> commit 213013a5a08d37bd29da167eece256be75cebe7c
> commit 0868ec95edd45394fcf583bf3f1cfa311e8a4c1d
> commit f836a482511f299034e84f2e153f31698904f92b
> commit 27f13805c97fcb517982009e2bfb3fd9ad6e413f
> commit 6e1ecba04f030e650e12edec2ad7a57530c661e4
> commit 506e737427861bc1d288c498723d63d56a8075ce
> commit 0edfdf950796befdb42ab9b2ef76c76483d9dbb1
>
> where I have edited out the text info. I am not able to detect the
> chronological sequence of these numbers. I understand that the first 8
> digits can be used as a shorthand, but these do not seem to be
> chronologically ordered either. For purposes of bug tracking it would be
> very helpful to be able to report a rev number that was chronologically
> ordered. Are there any plans to do so, or am I missing something really
> obvious here?
>
> Alvin
>
>
>
>
> --
> View this message in context: http://inkscape.13.x6.nabble.com/two-trivial-questions-concerning-the-gitlab-repository-tp4980326.html
> Sent from the Inkscape - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
>> then a query to the git tree will show you precisely where a certain commit is located

- how exactly would you perform such a query?
- what is the preferred format for reporting such a commit number in a bug report?

<somewhat off-topic, perhaps, but you need to remember that a lot of bug triage and analysis has in the past been performed by people who are not necessarily programmers, and who may not have a great deal of patience, or tolerance, for a system that has suddenly become extremely abstruse, to put it as politely as possible.>

Alvin

Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Maren Hachmann
For inkscape-web, we're using:
git log -1 --date=local --format="%cd (%h)"

resulting in
Thu Jun 15 18:07:08 2017 (a170251)

Maren

Am 23.06.2017 um 14:59 schrieb alvinpenner:

>>> then a query to the git tree will show you precisely where a certain
> commit is located
>
> - how exactly would you perform such a query?
> - what is the preferred format for reporting such a commit number in a bug
> report?
>
> <somewhat off-topic, perhaps, but you need to remember that a lot of bug
> triage and analysis has in the past been performed by people who are not
> necessarily programmers, and who may not have a great deal of patience, or
> tolerance, for a system that has suddenly become extremely abstruse, to put
> it as politely as possible.>
>
> Alvin
>
>
>
>
>
> --
> View this message in context: http://inkscape.13.x6.nabble.com/two-trivial-questions-concerning-the-gitlab-repository-tp4980326p4980330.html
> Sent from the Inkscape - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
thanks, on my system that produced the answer:

git log -1 --date=local --format="%cd (%h)"
Thu Jun 22 22:09:08 2017 (213013a)

I think this answer is probably correct since there was indeed a commit made at:
commit 213013a5a08d37bd29da167eece256be75cebe7c
Author: Felipe Corrêa da Silva Sanches <juca@members.fsf.org>
Date:   Thu Jun 22 23:09:08 2017 -0300

However, it does not exactly answer my question. Assume that someone has reported that a bug was fixed in commit number:
'0edfdf95'
How would I find out when this was done? In other words, what is the mechanism whereby someone can verbally report that a bug was fixed in a certain commit, and that someone else can independently confirm when it was fixed? Sorry to be a pest, but this is an essential feature of a bug reporting/fixing system.

Alvin

Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Terry Brown
On Fri, 23 Jun 2017 07:42:29 -0700 (MST)
alvinpenner <[hidden email]> wrote:

> thanks, on my system that produced the answer:
>
> git log -1 --date=local --format="%cd (%h)"
> Thu Jun 22 22:09:08 2017 (213013a)
>
> I think this answer is probably correct since there was indeed a
> commit made at:
> commit 213013a5a08d37bd29da167eece256be75cebe7c
> Author: Felipe Corrêa da Silva Sanches <[hidden email]>
> Date:   Thu Jun 22 23:09:08 2017 -0300
>
> However, it does not exactly answer my question. Assume that someone
> has reported that a bug was fixed in commit number:
> '0edfdf95'

/an/ answer at the end of my response below (somewhat out of sequence
because of email issues).

A project I work on uses YYYMMDDHHMMSS to ID commits (in addition to
the git hash).  Chances of two authors submitting at the same second
are minuscule.  I think, the way we set it up, it reports local time,
so that could be confusing in some cases.

We use that for a few reasons.  A download of a git commit can't
include its own hash.  Non-programmers probably understand
20170623075434 as a build ID more intuitively than 42da7b2.  The third
thing I forgot.

We use a git commit hook to update this value in a file the code reads
and reports at runtime, and also to add the number at the bottom of the
commit msg.  This only works when developers install the git hook
(trivial but easy to forget), so we just handle its absence gracefully.

If you just want to relate git hashes to dates:

git log --pretty='format:%H %ci'

(see https://git-scm.com/docs/git-log#_pretty_formats)

Cheers -Terry

> How would I find out when this was done? In other words, what is the
> mechanism whereby someone can verbally report that a bug was fixed in
> a certain commit, and that someone else can independently confirm
> when it was fixed? Sorry to be a pest, but this is an essential
> feature of a bug reporting/fixing system.
>
> Alvin
>
>
>
>
>
> --
> View this message in context:
> http://inkscape.13.x6.nabble.com/two-trivial-questions-concerning-the-gitlab-repository-tp4980326p4980332.html
> Sent from the Inkscape - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Felipe Sanches-2
In reply to this post by alvinpenner
2017-06-23 9:59 GMT-03:00 alvinpenner <[hidden email]>:
>>> then a query to the git tree will show you precisely where a certain
> commit is located
>
> - how exactly would you perform such a query?

visit the webpage:
https://gitlab.com/inkscape/inkscape/commit/0868ec95

replacing 0868ec95 with the actual commit you're interested in. That
will show you all the metadata such as author, commit date&time,
description, code changes, etc...

> - what is the preferred format for reporting such a commit number in a bug
> report?

Please, always refer to the commit hash when reporting a bug, because
that is absolutely the most precise way to refer to a commit
unambiguously.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Mattia Rizzolo
In reply to this post by Terry Brown
On Fri, Jun 23, 2017 at 10:10:15AM -0500, Terry Brown wrote:

> On Fri, 23 Jun 2017 07:42:29 -0700 (MST)
> alvinpenner <[hidden email]> wrote:
> > However, it does not exactly answer my question. Assume that someone
> > has reported that a bug was fixed in commit number:
> > '0edfdf95'
> > How would I find out when this was done? In other words, what is the
>
> If you just want to relate git hashes to dates:
>
> git log --pretty='format:%H %ci'
>
> (see https://git-scm.com/docs/git-log#_pretty_formats)
this would istantly show you that commit (I personally find `show` more
useful than `log` for this use case):
    git show 0edfdf95
If you want to change the current working tree to that commit so you can
e.g. try to build it there and do whatever you want to do:
    git checkout 0edfdf95


I can see that you feel a bit lost with git.  It's just a different
program with its own options that are different than bzr's, don't feel
angry toward it :)

--
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
In reply to this post by Terry Brown
    thanks for the advice, I like the idea of the date/time format.
as far as the log command is concerned, I have not been able to get it to work. Attached are some of the attempts I made, all of which failed. Do you have a specific example of how to use this command to get the date/time for a specific commit?
    again, I apologize for asking such obvious questions, but I find the git documentation to be unintelligible, and I am deliberately trying to approach this from the point of view of a non-expert user, not a programmer.

Alvin
...............................................................................................

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci'
fatal: ambiguous argument '%ci'': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci' 12345678
fatal: ambiguous argument '%ci'': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci' 0edfdf95
fatal: ambiguous argument '%ci'': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci' '0edfdf95'
fatal: ambiguous argument '%ci'': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci' commit 0edfdf95
fatal: ambiguous argument '%ci'': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci' commit <0edfdf95>
The syntax of the command is incorrect.

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H %ci' <0edfdf95>
The syntax of the command is incorrect.

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H' <0edfdf95>
The syntax of the command is incorrect.

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty='format:%H' 0edfdf95
'format:0edfdf950796befdb42ab9b2ef76c76483d9dbb1'
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
In reply to this post by Felipe Sanches-2
>> visit the webpage:
https://gitlab.com/inkscape/inkscape/commit/0868ec95

thanks for the advice. I agree that this command works, but it is not very user-friendly. It would be better if the log command could be used for this purpose, except that I have not yet figured out how...

Alvin

Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Gord Caswell
In reply to this post by alvinpenner
 According to the documentation, try removing the quotes as below.

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty=format:%H
%ci

---
From the desk of:

Gord Caswell

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
In reply to this post by Mattia Rizzolo
thanks for the help, I had good success with the command:

git log 0edfdf95

Well, that was embarrassingly easy. I think the problem was that the git documentation was attempting to teach me how to run, when I did not yet know how to crawl. A simple example is worth a thousand words.

sorry for the noise,
Alvin
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
one final comment and then I promise we will never speak of this again. It is possible that this is a Windows-specific issue. On Windows the format '%H %ci' is not acceptable while the format "%H %ci" works correctly, see below:

.......................................................................
C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty=format:'%H %ci' 0edfdf95
fatal: ambiguous argument '%ci'': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git log --pretty=format:"%H %ci" 0edfdf95
0edfdf950796befdb42ab9b2ef76c76483d9dbb1 2017-06-21 21:04:53 -0300
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Bryce Harrington-3
In reply to this post by Felipe Sanches-2
On Fri, Jun 23, 2017 at 12:23:38PM -0300, Felipe Sanches wrote:

> 2017-06-23 9:59 GMT-03:00 alvinpenner <[hidden email]>:
> >>> then a query to the git tree will show you precisely where a certain
> > commit is located
> >
> > - how exactly would you perform such a query?
>
> visit the webpage:
> https://gitlab.com/inkscape/inkscape/commit/0868ec95
>
> replacing 0868ec95 with the actual commit you're interested in. That
> will show you all the metadata such as author, commit date&time,
> description, code changes, etc...

Alvin, if you haven't already, try:

    git show 0868ec95

I find I use this command a lot.
 
> > - what is the preferred format for reporting such a commit number in a bug
> > report?
>
> Please, always refer to the commit hash when reporting a bug, because
> that is absolutely the most precise way to refer to a commit
> unambiguously.

In bug reports, a common practice I've seen in the linux and x.org
communities is to cut and paste the commit message, so like:


  Bug 123
  ------------------------------------------------------------------------
  > ...
  > In testing your suggested change, I no longer saw the issue.

  Great, thanks for testing.  Pushed:

  commit 0868ec95edd45394fcf583bf3f1cfa311e8a4c1d
  Author:     Felipe Corrêa da Silva Sanches <[hidden email]>
  AuthorDate: Thu Jun 22 21:56:51 2017 -0300
  Commit:     Felipe Corrêa da Silva Sanches <[hidden email]>
  CommitDate: Thu Jun 22 21:58:21 2017 -0300

      rename SPIVariableFontAxisOrNormal => SPIFontVariationSettings and
      implement full parsing of multiple axes and respective design-space
      coordiantes.
  ------------------------------------------------------------------------

For the triager it's no extra work to cut and paste the entire
description versus just the commit SHA, but it communicates a lot more
information to the reader.

Bryce

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Terry Brown
In reply to this post by alvinpenner
On Fri, 23 Jun 2017 09:21:24 -0700 (MST)
alvinpenner <[hidden email]> wrote:

> one final comment and then I promise we will never speak of this
> again. It is possible that this is a Windows-specific issue. On
> Windows the format '%H %ci' is not acceptable while the format "%H
> %ci" works correctly, see below:

Yes, that was my mistake, not really git related, unix command line
uses "" and '', with different but often interchangeable
effect, whereas Windows command line only uses "".

Cheers -Terry

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Eduard Braun
In reply to this post by alvinpenner
Am 23.06.2017 um 18:21 schrieb alvinpenner:
one final comment and then I promise we will never speak of this again. It is
possible that this is a Windows-specific issue. On Windows the format '%H
%ci' is not acceptable while the format "%H %ci" works correctly, [...]

You might try to ask / file an issue at https://github.com/git-for-windows/git/issues (maybe they know the answer, maybe it's an actual bug).

That being said there are alternatives to using git from cmd.exe that will make your life easier:
  • Use "Git Bash" (it ships with Git for Windows and provides a proper shell environment like it is available on Linux. It makes struggling with the limitations of the Windows command line unnecessary and already contains a lot of helpful tools (like 'diff')
  • Use MSYS2 (as a matter of fact Git for Windows is based on / compiled with MSYS2 and the "Git Bash" is basically an MSYS2 shell).
    I'd suggest you to look into it eventually anyway, since at this point I'd say MSYS2 is the recommended way to build Inkscape on Windows. I certainly won't touch devlibs for master anymore and I'm even considering to compile 0.92.2 with it, at least as a "beta" or "technology preview". All my development happens on MSYS2 nowadays.
  • Use "Git GUI". It ships with Git for Windows and simplifies stuff like looking at diffs and the log greatly.
  • Use a dedicated GUI front-end for Git. Personally I'm working a lot with SourceTree [1] which has a lot of features that I use regularly and are not convenient to use on the command line (at least for me), e.g.
    • looking at / searching in commit history
    • git blame
    • looking at commit diffs
    • staging / adding a list of files (simply by using checkboxes instead of specifying all filenames);
      it even supports staging parts of files (e.g. I can choose to exclude my debug output from a commit line-by-line - try that on a command line without crying!).

Regards,
Eduard

[1] https://www.sourcetreeapp.com/


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
thanks for all the help, I have submitted a bug report to git at:

https://github.com/git-for-windows/git/issues/1216

Alvin
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

Krzysztof Kosiński
There is also the command "git describe", which will show how many
commits were made from the most recent tag:

$ git describe --tags
INKSCAPE_0_92_PRE1-1666-gd010732ae4

1666 is the number of commits since Inkscape 0.92-pre1. However, this
is not a recommended way to identify commits.

2017-06-23 12:16 GMT-07:00 alvinpenner <[hidden email]>:

> thanks for all the help, I have submitted a bug report to git at:
>
> https://github.com/git-for-windows/git/issues/1216
>
> Alvin
>
>
>
> --
> View this message in context: http://inkscape.13.x6.nabble.com/two-trivial-questions-concerning-the-gitlab-repository-tp4980326p4980344.html
> Sent from the Inkscape - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: two trivial questions concerning the gitlab repository

alvinpenner
strange, in my case, when I run this command, I get:

C:\Users\penne_000\AppData\Roaming\InkscapeGit>git describe --tags
fatal: No names found, cannot describe anything.

Alvin
12