upstream/mercurial-mirror Files · mercurial/templates/raw/logentry.tmpl

lfs: narrow the exceptions that trigger a transfer retry...

lfs: narrow the exceptions that trigger a transfer retry The retries were added to workaround TCP RESETs in fb-experimental fc8c131314a9. I have no idea if that's been debugged yet, but this wide net caught local I/O errors, bad hostnames and other things that shouldn't be retried. The next patch will validate objects as they are uploaded, and there's no need to retry those errors. The spec[1] does mention that certain http errors can be retried, including 500. But let's work through the corruption detection issues first. [1] https://github.com/git-lfs/git-lfs/blob/master/docs/api/batch.md

Alexander Plavin - - Load All Authors

File last commit:

r19429:c8490dcc default


                r35491:b0c01a5e

default

Download file

             logentry.tmpl
        
                    6 lines
            
             | 172 B
            
                | application/x-cheetah
            
             |
                CheetahLexer
            
             / mercurial / templates / raw / logentry.tmpl
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      changeset:   {node}

      revision:    {rev}

      user:        {author}

      date:        {date|rfc822date}

      summary:     {desc}

      {branches%branchname}{tags%tagname}{bookmarks%bookmarkname}

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				changeset: {node}
				revision: {rev}
				user: {author}
				date: {date\|rfc822date}
				summary: {desc}
				{branches%branchname}{tags%tagname}{bookmarks%bookmarkname}