git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Feature suggestion: git-hist

From
H.Merijn Brand <h.m.brand@xs4all.nl>
Date
Jul 30, 2008, 13:58 UTC
Message-ID
<20080730155835.71289eee@pc09.procura.nl>
In-Reply-To
<20080730133334.GB31192@lars.home.noschinski.de>

On Wed, 30 Jul 2008 15:33:34 +0200, Lars Noschinski <lars-2008-1@usenet.noschinski.de> wrote:

Show 12 quoted lines
> * H.Merijn Brand <h.m.brand@xs4all.nl> [08-07-30 13:38]:
> 
> >	I can ask them what version they have, and I can then check if
> >	the complaint was already addressed in an update that was
> >	already released. In SCCS this was easy: they tell me the output
> >	of the what command, I check if the bug was fixed in a newer
> >	version and the answer is present. No such luck in git, as the
> >	stamps are (non-sequitive) SHA id's. As we moved to git, we now
> >	have to update those id's by hand, as the customers are used to
> >	it. (At least we can now use readable date formats)
> 
> Hm, what about "git-describe --contains $SHA_OF_BUGFIX"?

If you come from a SCCS environment, the developers are used to see the version of a single file, not of the id of a fix. One of the reasons we moved from SCCS to git, is that we now can commit a group of files as a single commit, and later look at the complete picture.

We are not used to working with $SHA's, and IMHO from the end-user pov, a $SHA is less user friendly than a release number or a file version. I can remember a version, but I cannot remember a SHA.

The end user only has the application, which is (or at least should be) able to spit out its release version. That is all we can go by when we dig back into the history to see where we changed things.

One (very) big disadvantage of SCCS is that commits are on a per-file basis, and only in a single directory. This drawback still haunts me in git, as my first attempts to convert were successful in a single folder and git cannot merge folders into a single project.

Say I now have

/work/src/project/.git /work/src/project/module_a/.git /work/src/project/module_b/.git /work/src/project/module_c/.git

Which are all converted repos from SCCS, I'd like to merge the three module_# repos into the top level repo.

-- 
H.Merijn Brand          Amsterdam Perl Mongers  http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, SuSE 10.1, 10.2, and 10.3, AIX 5.2, and Cygwin.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/
Previous: Lars NoschinskiNext: Miklos Vajna
Message 5 of 13 in “Feature suggestion: git-hist”
  1. H.Merijn BrandJul 30, 2008
  2. Pieter de BieJul 30, 2008
  3. H.Merijn BrandJul 30, 2008
  4. Lars NoschinskiJul 30, 2008
  5. H.Merijn BrandJul 30, 2008
  6. Miklos VajnaJul 30, 2008
  7. H.Merijn BrandJul 30, 2008
  8. Santi BéjarJul 30, 2008
  9. Avery PennarunJul 30, 2008
  10. Lars NoschinskiJul 30, 2008
  11. Santi BéjarJul 30, 2008
  12. H.Merijn BrandJul 30, 2008
  13. H.Merijn BrandJul 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.