Provide Option to Display only Changeset Hash in UI

Issue #312 wontfix
Former user created an issue

The incremental revision numbers are not that useful for a central repository. Allowing the option to configure the server so that only full hashes are displayed would make copy/paste from the web UI much easier (and also cut back on some of the visual noise).

Comments (6)

  1. Marcin Kuzminski repo owner

    Can you explain a little more ? It's little unclear to me what this task is about.

  2. Bart Schapendonk

    probably this

    It is a strictly local convenience identifier for a revision. It can be useful as it is shorter to type than the 40-digit hexadecimal string that uniquely identifies a revision.

    Revision numbers referring to changesets are very likely to be different in another copy of a repository. Do not use them to talk about changesets with other people. Use the changeset ID instead.

  3. Marcin Kuzminski repo owner

    Maybe i asked wrong question. Where in rhodecode are you having a numerical revisions that should be changed into a hash ?

  4. Former user Account Deleted

    Shortlog in the summary page, "revision" column has them like "r1833:a3ee2611e6e8". Everything before ":" can just go, it's rarely (if ever?) useful non-locally.

    Changelog and diff page, each commit has them like "commit 1833: a3ee2611e6e8@2011-12-01 23:15:26". Same as above.

  5. Marcin Kuzminski repo owner

    I disagree with that. I find it very helpfull. You can easily determine if the commit is one of first/last etc. You should use the numeric values for anything, but they are there to help. This will not be removed.

  6. Former user Account Deleted

    I disagree with your disagree (but we can agree to disagree I guess :)).

    In the summary and changelog pages, each commit is already laid out in numeric revision order. So you already implicitly know which one is "before" another one.

    Would it be possible to make that numeric revision an option? (e.g. in some per-user settings?) In our workflow we never ever need to look at that number, so it only clutters the summary / changelog views.

  7. Log in to comment