upstream/mercurial-mirror Files · hgext/infinitepush/schema.sql

absorb: make `--edit-lines` imply `--apply-changes`...

absorb: make `--edit-lines` imply `--apply-changes` One of our users tried to use `hg absorb -e` but it seemed that it would only bring up the editor if there were no changes the command could automatically detect destination for. I spent probably half an hour debugging why it worked that way. I finally figured out that it does bring up the editor, but you have to answer "yes" to the "apply changes" prompt *first*. That seems very unintuitive. If the user wants to edit the changes, there seems to be little reason to present them with a prompt first, so let's have `-e/--edit-lines` imply `-a/--apply-changes`. All the tests using `-e` also already used `-a`. I changed them to rely on the implied `-a` so we get coverage of that. Differential Revision: https://phab.mercurial-scm.org/D12550

Pulkit Goyal - - Load All Authors

File last commit:

r37204:03ff17a4 default


                r49945:0effaf9d

default

Download file

             schema.sql
        
                    33 lines
            
             | 1.1 KiB
            
                | text/x-sql
            
             |
                TransactSqlLexer
            
             / hgext / infinitepush / schema.sql
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        Pulkit Goyal
    
infinitepush: move the extension to core from fb-hgext...

              r37204
            
      CREATE TABLE `bookmarkstonode` (

        `node` varbinary(64) NOT NULL,

        `bookmark` varbinary(512) NOT NULL,

        `reponame` varbinary(255) NOT NULL,

        PRIMARY KEY (`reponame`,`bookmark`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

      CREATE TABLE `bundles` (

        `bundle` varbinary(512) NOT NULL,

        `reponame` varbinary(255) NOT NULL,

        PRIMARY KEY (`bundle`,`reponame`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

      CREATE TABLE `nodestobundle` (

        `node` varbinary(64) NOT NULL,

        `bundle` varbinary(512) NOT NULL,

        `reponame` varbinary(255) NOT NULL,

        PRIMARY KEY (`node`,`reponame`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

      CREATE TABLE `nodesmetadata` (

        `node` varbinary(64) NOT NULL,

        `message` mediumblob NOT NULL,

        `p1` varbinary(64) NOT NULL,

        `p2` varbinary(64) DEFAULT NULL,

        `author` varbinary(255) NOT NULL,

        `committer` varbinary(255) DEFAULT NULL,

        `author_date` bigint(20) NOT NULL,

        `committer_date` bigint(20) DEFAULT NULL,

        `reponame` varbinary(255) NOT NULL,

        `optional_json_metadata` mediumblob,

        PRIMARY KEY (`reponame`,`node`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

	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

Pulkit Goyal infinitepush: move the extension to core from fb-hgext...	r37204	CREATE TABLE `bookmarkstonode` (
		`node` varbinary(64) NOT NULL,
		`bookmark` varbinary(512) NOT NULL,
		`reponame` varbinary(255) NOT NULL,
		PRIMARY KEY (`reponame`,`bookmark`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;

		CREATE TABLE `bundles` (
		`bundle` varbinary(512) NOT NULL,
		`reponame` varbinary(255) NOT NULL,
		PRIMARY KEY (`bundle`,`reponame`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;

		CREATE TABLE `nodestobundle` (
		`node` varbinary(64) NOT NULL,
		`bundle` varbinary(512) NOT NULL,
		`reponame` varbinary(255) NOT NULL,
		PRIMARY KEY (`node`,`reponame`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;

		CREATE TABLE `nodesmetadata` (
		`node` varbinary(64) NOT NULL,
		`message` mediumblob NOT NULL,
		`p1` varbinary(64) NOT NULL,
		`p2` varbinary(64) DEFAULT NULL,
		`author` varbinary(255) NOT NULL,
		`committer` varbinary(255) DEFAULT NULL,
		`author_date` bigint(20) NOT NULL,
		`committer_date` bigint(20) DEFAULT NULL,
		`reponame` varbinary(255) NOT NULL,
		`optional_json_metadata` mediumblob,
		PRIMARY KEY (`reponame`,`node`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;