[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(computed-origin-method) and (origin)'s file-name field
|
From: |
Adam Faiz |
|
Subject: |
(computed-origin-method) and (origin)'s file-name field |
|
Date: |
Sun, 27 Aug 2023 20:25:48 +0800 |
Hello everyone,
I'm wondering about the solution to the computed-origin-method workaround...
Must the 'computed-origin-method' workaround be solved by adding the renaming
capability to snippets?
Why couldn't the file-name field of the source origin be used to rename it?
If it's because the upstream source might be confused with the liberated
version, couldn't a comment above the snippet clarify that?
- (computed-origin-method) and (origin)'s file-name field,
Adam Faiz <=